Thank you Vincent, it works great.
Is there a way to get a longer trace? (i.e. longer framing range
before a dump stack so to have a longer history?)
2006/6/9, Vincent Snijders <[EMAIL PROTECTED]>:
Alexandre Leclerc wrote:
> I'm getting nothing (no file after execution). I did activate the -g
> compiler switch to use gdb.exe. I also tried directly in gdb but got
> nothing.
>
> 2006/6/9, Vincent Snijders <[EMAIL PROTECTED]>:
>
>> Alexandre Leclerc wrote:
>> > I would like to use gdb to have a backtrace of all that is done in the
>> > application while it runs and after examine it. I have to errors, I
>> > only want to examine mouse messages stuff and how the passing of the
>> > message is done.
>> >
>> > I want to know why the mouse click are not good when trying to dock a
>> > form in the onther one.
>> >
>>
>> If you want to analyze after having run you program, I would add
>> DumpStack at places where you want to inspect a back trace.
>>
>> http://lazarus-ccr.sourceforge.net/docs/lcl/lclproc/dumpstack.html
>>
>> (Documentation needed, but at least it mentions the unit).
>>
>> Vincent
>>
The output is written using debugln, see FAQ for more info:
http://wiki.lazarus.freepascal.org/index.php/Lazarus_Faq#How_can_I_see_debug_output.3F
Vincent
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
--
Alexandre Leclerc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
