[fpc-devel] Better Call Stack Information
Sven Barth
pascaldragon at googlemail.com
Sat Aug 9 12:52:19 CEST 2014
On 08.08.2014 16:20, mark diener wrote:
> Using Lazarus 1.2.4 win32 on Windows 8.1
>
> I am getting stack traces like this:
>
> #0 SYSTEM_FINISH_WAITFIXEDLIST$PFREELISTS at :0
> #1 ?? at :0
> #2 ?? at :0
> #3 TRPZUDPSRV__EXECWRAPPER(<error reading variable>) at
> C:\pdev\rpzlib\rpzudpsrv.pas:225
> #4 TRPZUDPSRV__EXECUTE(<error reading variable>) at
> C:\pdev\rpzlib\rpzudpsrv.pas:171
> #5 CLASSES_THREADPROC$POINTER$$LONGINT at :0
> #6 SYSTEM_THREADMAIN$POINTER$$LONGINT at :0
> #7 KERNEL32!CreateWaitableTimerA at :0
> #8 ?? at :0
> #9 ?? at :0
> #10 ?? at :0
> #11 ?? at :0
>
>
> There is a stubborn bug for example at this line:
>
> 225: application.QueueAsyncCall(@self.guitikfunc,nres);
>
> That is the last traceable part of the source code.
>
> Does anybody know how to enable full code tracing in the system,
> sysutils, etc to cover calls like
> QueueAsyncCall( ) etc.
You'll need to recompile the RTL and packages with debug information
(OPT="-gl" for the "make" command line). QueueAsyncCall should normally
be debuggable as AFAIK the LCL is usually compiled with debug information...
Regards,
Sven
More information about the fpc-devel
mailing list