<!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>
> Follow up to this - a simple patch (attached) allows the rtl source to <br>
> show, rather than the assembler window. However there seems to be a more <br>
> fundamental problem, in that a "step into" that ends up stepping into a <br>
> rtl routine like fpc_shortstr_SInt reports a SIGSEGV in the debugged <br>
> program, when no such exception has occurred.<br>
<br>
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?<br>
<br>
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.<br>
<br>
In the second case, it's difficult to say what happens, since 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>
Joost.</FONT>
</P>
</BODY></HTML>