[Lazarus] Need testers for the a new debugger

[Joost van der Sluis]

> Follow up to this - a simple patch (attached) allows the rtl source to 
> show, rather than the assembler window. However there seems to be a more 
> fundamental problem, in that a "step into" that ends up stepping into a 
> rtl routine like fpc_shortstr_SInt reports a SIGSEGV in the debugged 
> program, when no such exception has occurred.

Did you step directly into fpc_shortstr_SInt, or did you do a 'step into', and did it eventually arrived at fpc_shortstr_SInt, because it was the first procedure with debug-info?

In the first case, a software-debug breakpoint is set, which is probably not removed correctly. In that case the debuggee does SIGSEGV, only it will only do this because the debugger did change it's code.

In the second case, it's difficult to say what happens, since hardware-breakpoints are used in that case.

Do you get a message on the console like 'failed to write data at xxxxxx'?

Joost.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20140719/f180baef/attachment-0003.html>