[fpc-devel] Better Call Stack Information

[mark diener]

Sven:

Thanks for your response.

I am able to recompile RTL with the following commands issues from an Admin
level DOS prompt:

make clean
make all OS_TARGET=win32 CPU_TARGET=i386 OPT="-gl -O-"
make install OS_TARGET=win32 CPU_TARGET=i386

How do I point the compiler to look at the new units/*.ppu

Currently, the Lazarus 1.2.4/ Fpc 2.6.4 installation puts the stock RTL
units into C:\lazarus\fpc\2.6.4\units\i386-win32\
and the newly compiled RTL units into
C:\lazarus\fpc\2.6.4\source\rtl\units\i386-win32

Where would I change the internal paths of the compiler so that it now
looks at the source code
and the newly compiled *.o / *.ppu files of the recompiled RTL instead of
looking in the original spot?

Or must I copy the new compiled stuff into the location of the original
ppu/object files?

Thanks,

marco


On Sat, Aug 9, 2014 at 4:52 AM, Sven Barth <pascaldragon at googlemail.com>
wrote:

> 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
>
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20140810/1a279f50/attachment.html>