Joost van der Sluis
joost at cnoc.nl
Fri Mar 27 16:28:38 CET 2015
On 03/27/2015 02:53 PM, Sven Barth wrote:
> Am 27.03.2015 14:17 schrieb "Joost van der Sluis" <joost at cnoc.nl
> <mailto:joost at cnoc.nl>>:
> > But I think that debuggers nowadays are more clever, they detect that
> the breakpoint is actually self-inflicted, and so they decide to
> continue. After all: the developer can have it's reasons to call this
> interrupt, and the debugger should not influence normal execution.
> This might be true on an embedded system, but if you run any of the
> normal OSes where you can't modify interrupt handlers anyway then on
> x86(_64) INT 3 (or $CC) /always/ means breakpoint. And from experience I
> know that both GDB and WinDBG respect these as they should.
It should result in a sigtrap (it *IS* a sigtrap), and the debugger can
stop on those. But that's something else than the debugger report a stop
at a breakpoint.
More information about the Lazarus