<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/02/2016 02:47, Luiz Americo
Pereira Camara wrote:<br>
</div>
<blockquote
cite="mid:CA+nZ=yOHfBqvnQiUyEsw4cuHvPgGSeHXJd-jXGw79AKV_Qp3PA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div><br>
</div>
I compiled a program with -Xg (generating an external
debug info file *.dbg)<br>
<br>
</div>
And deployed the executable without the debug info<br>
<br>
</div>
When an exception occurs i get a backtrace with only
addresses<br>
<br>
</div>
How to get the line number, method names of the backtrace
using the external debug file?<br>
<br>
</div>
</div>
</div>
</blockquote>
I don't know how to do it with an external dbg file. (though gdb
might be able do to that)<br>
<br>
But the following works (at least if the exe is not compiled for
dynamic relocation)<br>
<br>
- Build an exe with debug in the exe.<br>
- Make a copy and strip debug from the copy<br>
- Ship the copy<br>
<br>
Lazarus has "Leaks and Traces" in the view menu. Paste the trace,
and then use the Button "Resolve" to load the exe with symbols. That
should do.<br>
<br>
It uses a copy of the code found in infodwrf and "whatever the name
of the unit reading stabs". Both of them (afaik) dont do dbg files.
If someone has info how to add that, well ....<br>
<br>
<br>
as for gdb, you can open your exe (and if gdb finds the dbg file,
then that should be fine.)<br>
if gdb loaded your dbg info, then you can do something (not
tested/from memory)<br>
<pre><font size="-1">info symbol 0x54320
and it prints what is at that address. Do that for each address in the trace.
</font></pre>
<br>
</body>
</html>