[fpc-devel] Debugging FPC

Jonas Maebe jonas.maebe at elis.ugent.be
Sat Apr 5 15:09:35 CEST 2008

On 05 Apr 2008, at 14:57, Никита Баль wrote:
>> With which version of gdb? Which version of FPC did you compile, and
>> with which version of FPC did you compile it? And with which command
>> line options (the ones you show above don't include any debug
>> generation information, so there must be more)?
> Lazarus version - 0.9.24 beta
> FPC compiler version - 2.2.0 [2007/11/14] for i386
> GDB version - 6.6
> FPC sourse version - 2.2.0
> When i changed command line
> From:
>  -Fui386 -Fusystems -Fu../rtl/units/i386-win32 -Fii386 -FE. -FUi386/ 
> units/i386-win32 -di386 -dGDB -dBROWSERLOG -Fux86
> To:
>  -di386 -Fu../rtl/units/i386-win32 -FE. -FUi386/units/i386-win32 - 
> dGDB -dBROWSERLOG -gc -gd -gh -gl -gp -gt -gv -gw
> error changed too.
> new error: "Project pp raised exception class 'Unknown'"

That command line does not make sense. The compiler can only generate  
one kind of debug info at a time, while you are specifying three (-gd,  
-gv and -gw). Further, -gv does not generate info which is usable for  
debugging, but only for use with valgrind. You should use either -g or  
-gw (and not -gd; that switch has been removed from the current  
compiler versions).

See the manual or the compiler help pages for what the other switches  
mean. I don't know how well -gc and -gp work nowadays, so I'd leave  
those out as well.


More information about the fpc-devel mailing list