* Eli Zaretskii (2006-08-03) writes:

> Put a watchpoint to watch *(char *)0x85f988, and see what code
> modifies it.

Thanks for the hint.  That's what I get when playing around with it a
little bit (control characters replaced by strings again):

Breakpoint 1, w32_wnd_proc (hwnd=0x101f0, msg=43, wParam=0, lParam=552399328) 
at w32fns.c:3571
(gdb) p title
$1 = 0x860720 "G"
(gdb) delete
Delete all breakpoints? (y or n) y
(gdb) watch *(char *)0x860720
Hardware watchpoint 2: *(char *) 8783648
(gdb) c
Continuing.
Hardware watchpoint 2: *(char *) 8783648

Old value = 71 'G'
New value = -18 '\356'
0x7c913105 in _libkernel32_a_iname ()
(gdb) c
Continuing.
Hardware watchpoint 2: *(char *) 8783648

Old value = -18 '\356'
New value = 0 '\0'
0x7c911231 in _libkernel32_a_iname ()
(gdb) c
Continuing.
Hardware watchpoint 2: *(char *) 8783648

Old value = 0 '\0'
New value = -18 '\356'
0x7c913105 in _libkernel32_a_iname ()
(gdb) 

Hm, a Google search regarding _libkernel32_a_iname revealed nothing
really interesting.

-- 
Ralf



_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Reply via email to