<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/05/2013 16:35, silvioprog wrote:<br>
</div>
<blockquote
cite="mid:CAKq_V2LzWyDZoYKTy1kQW3n-bHokPzmZQaLEFqC6tjVxk7EaHA@mail.gmail.com"
type="cite">
<div dir="ltr">2013/5/8 silvioprog <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:silvioprog@gmail.com"
target="_blank">silvioprog@gmail.com</a>></span><br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">2013/5/8 Martin <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:lazarus@mfriebe.de" target="_blank">lazarus@mfriebe.de</a>></span><br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px
0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<div>[...]</div>
</div>
<div class="im"> Sorry, no that was not fixed.<br>
<br>
I was told something about path loading. That
was hopped to fix initial issue. Is that also
still there?<br>
<br>
Can you try the 2 debugln?<br>
<br>
Because we still need to find out who is the
right person to look at this after all<br>
<br>
<br>
Sorry about the mess.</div>
</div>
</blockquote>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><br>
</div>
No problem friend. :)<br clear="all">
<div><br>
</div>
<div>I'll do it now, a minute...</div>
</div>
</div>
</blockquote>
</div>
<div class="gmail_extra"><br>
</div>
Done:</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">
<div><a moz-do-not-send="true"
href="http://pastebin.com/HC7bcTay">http://pastebin.com/HC7bcTay</a><br>
</div>
<br>
</div>
</div>
</blockquote>
<br>
Ok. dumb question on my site: did the assembler window show, or did
it work without it?<br>
Because I cant see the asm stuff in the log.<br>
<br>
<br>
Well looking for it, I can now see it way down. But a completely
different situation, <br>
*stopped,reason="signal-received",signal-name="SIGPIPE",signal-meaning="Broken
pipe<br>
That triggers different code...<br>
<br>
<br>
So question: has the original issue been resolved ? <br>
<br>
<br>
<br>
About the new one, I can see what happens.<br>
<br>
The stopped position does not have debug info, so it can not
display.<br>
It should try to find a position on the stack....<br>
<br>
That fails. And it fails because it is exclusively disabled at that
time....<br>
<br>
I am not sure of the exact reasons... But IIRC it would give
source-editor the hickups (crash it) if it was allowed.<br>
I might find time to investigate that again, but I don't know.
Otherwise, this will need to wait. The original plan to resolve it
requires a big rewrite.<br>
<br>
<br>
On your own risk:<br>
debugger/gdbmidebugger line 5185<br>
<br>
<br>
function TGDBMIDebuggerCommandExecute.ProcessStopped(const AParams:
String;<br>
.......<br>
procedure ProcessSignalReceived(const AList: TGDBMINameValueList);<br>
.......<br>
<br>
FTheDebugger.QueueExecuteLock;<br>
try<br>
if not AIgnoreSigIntState<br>
or not SigInt<br>
then ProcessFrame(F);<br>
finally<br>
FTheDebugger.QueueExecuteUnlock;<br>
end;<br>
end;<br>
<br>
remove the lock and unlock.<br>
<br>
IIRC it is tricky to get the crash. So you might get a long way
before it happens<br>
</body>
</html>