[Lazarus] Need testers for the a new debugger

[Joost van der Sluis]

> > 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'?
> >
> 
> Just tried it again - it doesn't seem to be consistent. The specific was 
> stepping into a routine, and the problem seems to happen when stepping 
> "into" at the first begin. Trying it just now the debugger step into in 
> these circumstances - it now exits the routine. There are lots of 
> "Failed to read data at address $10B70F08C08347F8 from processid 11321. 
> Errcode: 5
> Failed to read data at address $E8000000C766D388 from processid 11321. 
> Errcode: 5
> Failed to read data at address $E8000000C766D388 from processid 11321. 
> Errcode: 5
> Failed to read data at address $E8000000C766D388 from processid 11321. 
> Errcode: 5
> Failed to read data at address $E8000000C766D388 from processid 11321. 
> Errcode: 5
> Failed to read data at address $E8000000C766D388 from processid 11321. 
> Errcode: 5"

Can you run Lazarus in a debugger (gdb, but in principle fpdebug is also possible ;) ) and set a breakpoint on fpdbglinuxclasses.pas:591. This is the line where the error above is printed. Then please try to reproduce the problem, and send me a backtrace when that breakpoint is hit.

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