Bug 4289: Debugging and dissasembly

James Trotter james.trotter at gmail.com
Sat Jan 14 04:21:53 CST 2006


A few days ago I filed this bug: http://bugs.winehq.org/show_bug.cgi?id=4289

Alexandre commented that there most likely was some stack corruption, and
that I should try and disassemble a few instructions before the crash and
look for API calls.

Now, I haven't used gdb or winedbg that much before, and I'm a bit uncertain
what to do. I understand that using the disassemble [<addr>][,<addr>]
command, the debugger will disassemble that address space. Given the stack
trace as in the bug report, which addresses, exactly, should I disassemble?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20060114/a6340272/attachment.htm

More information about the wine-devel mailing list