Re: hardware watchpoint does not stop with the value modified
小林佑矢 <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAEtoynbhCX0DHqOPexW1NW9+m8rJnBw6gjTuJCskWETnca=AuQ@mail.gmail.com> |
The assertion caused by my modification. First, I modified QEMU to trap memory access, but the assertion showed me that it does not work as intented. Next, I try to get call stack when the memory write occurs with watchpoint. But I can't do that as I wrote in the first mail. Sorry for confusing. Kobayashi 2016-03-29 20:19 GMT+09:00 Yao Qi <[email protected]>: > YuyaKobayashi <[email protected]> writes: > >> (gdb) c Continuing. >> [Thread 0x7fffc2dad700 (LWP 3162) exited] >> [New Thread 0x7fffc2dad700 (LWP 3169)] >> [Thread 0x7fffc2dad700 (LWP 3169) exited] >> [New Thread 0x7fffc2dad700 (LWP 3173)] qemu: >> /home/nutsman/git_repo/M-QEMU/qemu-2.3.1/exec.c:3007: ldl_phys_internal: >> Assertion `val1 == val' failed. > > Looks the assertion is triggered, and it probably means there is > something wrong in QEMU. You need to fix the QEMU problem first or > change to a different version of QEMU. > > -- > Yao (齐尧)