wine-devel at sun.consumer.org.il
Wed Jul 24 00:12:47 CDT 2002
Personally, I do:
some meaningless nop;
And then set or clear the breakpoint on the nop if I want. This gives me
debug time control over the breakpoint without giving up on the flexability.
David Hammerton wrote:
>You could do a "raise(SIGSTOP)", or if your lazy, "raise(19)".
>Replace SIGSTOP with your faviourate signal.
>I know that works when debugging with gdb, I guess it should with winedbg...
>On Thu, 25 Jul 2002 01:08:51 +0200, Max wrote:
>| Maybe it's a stupid question, but... is there a way to hard-code a
>| breakpoint ? I need to check a bit of code that gets called too many times and
>| I'd like to put a conditional breakpoints compiled in code; no way to use
>| winedbg built-in conditional breaks, the condition is too complicated.....
More information about the wine-devel