http://bugs.winehq.org/show_bug.cgi?id=24676
Eric Pouech eric.pouech@orange.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@orange.fr
--- Comment #1 from Eric Pouech eric.pouech@orange.fr 2010-10-09 03:38:46 CDT --- I can't reproduce what you describe. Wine-dbg>break mscenccomm!MSC_USBConnect fixme:dbghelp_dwarf:compute_location Only supporting one breg (18 -> 24) Many symbols with name 'mscenccomm!MSC_USBConnect', choose the one you want (<cr> to abort): [1]: 0x100011e0 MSC_USBConnect in mscenccomm [2]: 0x100011e0 MSC_USBConnect in mscenccomm => 1 Breakpoint 1 at 0x100011e0 MSC_USBConnect in mscenccomm Wine-dbg>c Stopped on breakpoint 1 at 0x100011e0 MSC_USBConnect in mscenccomm Wine-dbg>stepi 17 0x10001a3f: call *%esi Wine-dbg>nexti 10 0x10001a5d: movl %eax,%ebp
which works flawlessly afterwards. Are you sure you haven't set other breakpoints (on addresses which are not instructions boundaries? => this could explain why you get different instructions at the end) btw, try also hardware breakpoints, they don't have the defaults of modifying instructions code.