Em 21/02/2012, às 18:38, Everton Vieira escreveu:
>
> 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
2012/2/20 Martin
> On 20/02/2012 15:52, Everton Vieira wrote:
>
> Is supposed that with the -gl and the BackTraceStrFunc would get all the
> info with the line number as well? Because if is true i've seen not work
> and could test again.
>
> It is supposed, yes.
> And it does for me.
>
> However
2012/2/20 Sven Barth
> Am 20.02.2012 16:52, schrieb Everton Vieira:
>
> Is supposed that with the -gl and the BackTraceStrFunc would get all the
>> info with the line number as well? Because if is true i've seen not work
>> and could test again.
>>
>
> This only works if you do not strip the deb
On 20/02/2012 15:52, Everton Vieira wrote:
Is supposed that with the -gl and the BackTraceStrFunc would get all
the info with the line number as well? Because if is true i've seen
not work and could test again.
It is supposed, yes.
And it does for me.
However I read something, someone said tha
Am 20.02.2012 16:52, schrieb Everton Vieira:
Is supposed that with the -gl and the BackTraceStrFunc would get all the
info with the line number as well? Because if is true i've seen not work
and could test again.
This only works if you do not strip the debug info from the executable
(either by
Is supposed that with the -gl and the BackTraceStrFunc would get all the
info with the line number as well? Because if is true i've seen not work
and could test again.
2012/2/20 Sven Barth
> Am 20.02.2012 16:34, schrieb Martin:
>
> If you do not want to ship with debug info:
>>
>> - compile with
Am 20.02.2012 16:34, schrieb Martin:
If you do not want to ship with debug info:
- compile with debug info
- keep a copy of the file with debug info
- use strip[.exe] to remove the debug info from shipping version
- dump addresses
when you get the addresses, you can use gdb and the copy with de
I've tried sometimes to do directly with the -gl and the BackTraceStrFunc
and i never was able to get the info of the error, maybe my fault. With
this units that i've passed i was able to get the info of the error with
the line number and everything else within the app.
2012/2/20 Martin
> On 20/
Am 20.02.2012 16:08, schrieb Everton Vieira:
I use this units to do that. Was someone with the nickname crhonos who made.
These units will only work if the debug format is Stabs and not DWARF.
Regards,
Sven
___
fpc-pascal maillist - fpc-pascal@lis
On 20/02/2012 14:58, leledumbo wrote:
I want to log the full runtime-error/exception backtrace to a file. I've
tried all methods explained
http://wiki.lazarus.freepascal.org/Logging_exceptions here but none seems
to give the full backtrace. i.e. when compiled with -gl, instead of just the
addres
Am 20.02.2012 15:58, schrieb leledumbo:
I want to log the full runtime-error/exception backtrace to a file. I've
tried all methods explained
http://wiki.lazarus.freepascal.org/Logging_exceptions here but none seems
to give the full backtrace. i.e. when compiled with -gl, instead of just the
addr
I use this units to do that. Was someone with the nickname crhonos who made.
2012/2/20 leledumbo
> I want to log the full runtime-error/exception backtrace to a file. I've
> tried all methods explained
> http://wiki.lazarus.freepascal.org/Logging_exceptions here but none seems
> to give the full
12 matches
Mail list logo
