<html>
<head>
<meta content="text/html; charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/08/2012 16:11, Marc Santhoff
wrote:<br>
</div>
<blockquote cite="mid:1344784292.1645.7.camel@puma.das.netz"
type="cite">
<pre wrap="">Am Sonntag, den 12.08.2012, 00:51 +0100 schrieb Martin:</pre>
<blockquote type="cite">
<pre wrap="">I don't know what exactly is going wrong on the Freebsd gdb. And I
havent used FreeBSD in a long time...
Where did he 6.1 debugger come from? Lazarus does not include GDB except
on windows (afaik).
</pre>
</blockquote>
<pre wrap="">
It's what comes with the system by default. Part of the OS.
</pre>
<blockquote type="cite">
<pre wrap="">I am surprised that Freebsd 9 should by default have such an old GDB.
</pre>
</blockquote>
<pre wrap="">
I'm used to it. It has been some versions back ever since. Or the other
way round, FreeBSD is a bit conservative and Linux adopts any new (and
maybe buggy) version very early. ;)</pre>
</blockquote>
"A bit conservative" 6.1 is years behind. Current is 7.4 (and 7.5 is
due)<br>
<br>
But that's not the point, there must be some other difference, maybe
it's localized, maybe it has bsd specific patches. It does somehow
behave different.<br>
<br>
<blockquote cite="mid:1344784292.1645.7.camel@puma.das.netz"
type="cite">
<blockquote type="cite">
<pre wrap="">Also, there must be something different about that GDB, since on Windows
GDB 5.2 does work....
</pre>
</blockquote>
<pre wrap="">
Running a program and triggering gdb on exception has worked for me all
the time until now. All the time is since ... um, I think 2001 or so,
with fpc 1.9.2. Real debugging - stepping through code, inspecting vars
- has worked only sometimes and partly. So that's no surprise regarding
FreeBSD.</pre>
</blockquote>
Well if you do not mind, you can still send me a full log <br>
<br>
<pre style="margin: 0; padding: 0;"><code class="bbc_code"> --debug-log=/home/yourname/laz.log --debug-enable=DBG_CMD_ECHO,DBG_STATE,DBG_DATA_MONITORS,DBGMI_QUEUE_DEBUG,DBGMI_TYPE_INFO,DBG_WARNINGS
If it is trivial to fix ...
</code></pre>
<br>
<br>
<br>
</body>
</html>