Re : Coded breakpoints

[Max]

Never mind, if WAS a stupid question :-)
For who needs it too, just add

__asm__("int $0x03\n\t") ;

at the required point, maybe inside an huge if(....)

Regards

Max

[Vincent Béron]

Le mer 24/07/2002 à 19:31, Max a écrit :
> Never mind, if WAS a stupid question :-)
> For who needs it too, just add
>
> __asm__("int $0x03\n\t") ;
>
> at the required point, maybe inside an huge if(....)

Or just a normal breakpoint after the innermost if, on a valid but
useless statement. No?

Vincent

[Massimo]

Thanx to all for answers !
I was thinking about it since one week... hemmm ... :-)

Another question... There's someone that have tested borland debugger in remote 
mode with wine ? I did it but without success.... I think it's one of most confortable 
debuggers out there, but had no success yet to make remote part to communicate 
with the gui part....

Regards

Max

Subject:        	Re: Re : Coded breakpoints
From:           	Vincent Béron <vberon(a)mecano.gme.usherb.ca>
To:             	max(a)veneto.com
Copies to:      	wine-devel(a)winehq.com
Date sent:      	23 Jul 2002 19:58:58 -0400
> Le mer 24/07/2002 à 19:31, Max a écrit :
> > Never mind, if WAS a stupid question :-)
> > For who needs it too, just add
> >
> > __asm__("int $0x03\n\t") ;
> >
> > at the required point, maybe inside an huge if(....)
>
> Or just a normal breakpoint after the innermost if, on a valid but
> useless statement. No?
>
> Vincent

[P. Christeas]

> Never mind, if WAS a stupid question :-)
> For who needs it too, just add
>
> __asm__("int $0x03\n\t") ;
>
> at the required point, maybe inside an huge if(....)
>
> Regards
>
> Max

Just one objection:
it is bad programming style to use assembly inside C. There are so many C 
functions and macro definitions, that wrap almost any processor instruction 
(I recently came accross the 3Dnow fn's). They are much better, because they 
will refuse to compile if sth goes wrong.
Say:
#define DBG_BREAK  { MY_WARN("I'm brreaking here..."); \
	__asm__("int $0x03\n\t"); }

end later use:
	DBG_BREAK
whenever you want. In addition you 'll be able to
#define DBG_BREAK { /* these brackets won't break conditionals */  }
to disable the breakpoint feature..