Bug 4289: Debugging and dissasembly

[James Trotter]

Hi!

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?

Thanks,
James