<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="Zarafa HTML builder 1.0">
<TITLE></TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT STYLE="font-family: courier" SIZE=2>
> > Did you step directly into fpc_shortstr_SInt, or did you do a 'step<br>
> > into', and did it eventually arrived at fpc_shortstr_SInt, because it<br>
> > was the first procedure with debug-info?<br>
> ><br>
> > In the first case, a software-debug breakpoint is set, which is probably<br>
> > not removed correctly. In that case the debuggee does SIGSEGV, only it<br>
> > will only do this because the debugger did change it's code.<br>
> ><br>
> > In the second case, it's difficult to say what happens, since<br>
> > hardware-breakpoints are used in that case.<br>
> ><br>
> > Do you get a message on the console like 'failed to write data at xxxxxx'?<br>
> ><br>
> <br>
> Just tried it again - it doesn't seem to be consistent. The specific was <br>
> stepping into a routine, and the problem seems to happen when stepping <br>
> "into" at the first begin. Trying it just now the debugger step into in <br>
> these circumstances - it now exits the routine. There are lots of <br>
> "Failed to read data at address $10B70F08C08347F8 from processid 11321. <br>
> Errcode: 5<br>
> Failed to read data at address $E8000000C766D388 from processid 11321. <br>
> Errcode: 5<br>
> Failed to read data at address $E8000000C766D388 from processid 11321. <br>
> Errcode: 5<br>
> Failed to read data at address $E8000000C766D388 from processid 11321. <br>
> Errcode: 5<br>
> Failed to read data at address $E8000000C766D388 from processid 11321. <br>
> Errcode: 5<br>
> Failed to read data at address $E8000000C766D388 from processid 11321. <br>
> Errcode: 5"<br>
<br>
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.<br>
<br>
Joost.</FONT>
</P>
</BODY></HTML>