Re: [fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-21 Thread Everton Vieira
Em 21/02/2012, às 18:35, Martin escreveu: > On 21/02/2012 20:28, Everton Vieira wrote: >> Em 21/02/2012, às 14:20, Martin escreveu: >> >>> On 21/02/2012 16:14, leledumbo wrote: > So the savest way to ensure that BackTraceStrFunc returns more than just the address us to use "-gl"

Re: [fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-21 Thread Martin
On 21/02/2012 20:28, Everton Vieira wrote: Em 21/02/2012, às 14:20, Martin escreveu: On 21/02/2012 16:14, leledumbo wrote: So the savest way to ensure that BackTraceStrFunc returns more than just the address us to use "-gl" I think I'm not clear enough to say that I have used -gl for this,

Re: [fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-21 Thread Everton Vieira
Em 21/02/2012, às 14:20, Martin escreveu: > On 21/02/2012 16:14, leledumbo wrote: >>> So the savest way to ensure that BackTraceStrFunc returns more than just >> the address us to use "-gl" >> >> I think I'm not clear enough to say that I have used -gl for this, and I >> don't get the line info

Re: [fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-21 Thread Martin
On 21/02/2012 16:14, leledumbo wrote: So the savest way to ensure that BackTraceStrFunc returns more than just the address us to use "-gl" I think I'm not clear enough to say that I have used -gl for this, and I don't get the line information. I've tried this on 2 places: ExceptProc and TAppl

[fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-21 Thread leledumbo
> So the savest way to ensure that BackTraceStrFunc returns more than just the address us to use "-gl" I think I'm not clear enough to say that I have used -gl for this, and I don't get the line information. I've tried this on 2 places: ExceptProc and TApplication.OnException. -- View this messa

Re: [fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-21 Thread Sven Barth
Am 20.02.2012 23:37 schrieb "leledumbo" : > > > The resolution of file and address can only be done if your code is a) > compiled with debug info and b) some code is available that can > translate the debug info to the output. The first is done by "-g", while > the second is done by adding the "l"

[fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-20 Thread leledumbo
> The resolution of file and address can only be done if your code is a) compiled with debug info and b) some code is available that can translate the debug info to the output. The first is done by "-g", while the second is done by adding the "l" option. The latter adds the unit lineinfo or lnf

[fpc-pascal] Re: Logging full runtime-error/exception backtrace

2012-02-20 Thread leledumbo
> I use this units to do that. Was someone with the nickname crhonos who made. Thanks, I'll try it :) -- View this message in context: http://free-pascal-general.1045716.n5.nabble.com/Logging-full-runtime-error-exception-backtrace-tp5499290p5500483.html Sent from the Free Pascal - General mailin