Hello Florian,
2017-07-22 13:49 GMT+01:00 Florian Klämpfl :
> Am 22.07.2017 um 14:47 schrieb Matias Vara:
> > Hello,
> >
> > I am not sure why my executable does not contains a .debug_aranges
> section. It contains .debug_line
> > and .debug_info. Am I missing some linker flags?
> >
>
> Maybe not
Am 22.07.2017 um 14:47 schrieb Matias Vara:
> Hello,
>
> I am not sure why my executable does not contains a .debug_aranges section.
> It contains .debug_line
> and .debug_info. Am I missing some linker flags?
>
Maybe not included by the linker script?
Hello,
I am not sure why my executable does not contains a .debug_aranges section.
It contains .debug_line and .debug_info. Am I missing some linker flags?
Thanks, Matias.
2017-07-19 0:05 GMT+01:00 Matias Vara :
> Hello Charlie and thanks for the comments. I ended up by implementing my
> own In
Hello Charlie and thanks for the comments. I ended up by implementing my
own Infodwrf unit.
Matias
On 18 Jul 2017 11:48 p.m., "Karoly Balogh (Charlie/SGR)" <
char...@scenergy.dfmk.hu> wrote:
Hi,
On Mon, 17 Jul 2017, Matias Vara wrote:
> Hello everyone, I am trying to port the code for backtrac
Hi,
On Mon, 17 Jul 2017, Matias Vara wrote:
> Hello everyone, I am trying to port the code for backtrace, e.g.,
> GetLineInfo(), to my freepascal kernel in order to print a backtrace
> when an exception happens.
Slightly off topic, but make sure when you copy code from (or even study
the source
Hello everyone, I am trying to port the code for backtrace, e.g.,
GetLineInfo(), to my freepascal kernel in order to print a backtrace when
an exception happens. The drawback now is that I am not sure where the
source is. I think it is the unit lnfodwrf.pp however I am not sure. From
the code, it s
