[fpc-devel] Problem with compilation (unknown crash)

Michel Catudal mcatudal at comcast.net
Wed Nov 14 01:15:57 CET 2012


Le 13/11/2012 08:11, Jonas Maebe a écrit :
> On 13 Nov 2012, at 02:08, Michel Catudal wrote:
>
>> Le 12/11/2012 07:34, Jonas Maebe a écrit :
>>> On 12 Nov 2012, at 13:32, Michel Catudal wrote:
>>>
>>>> Is there a way to figure out when a crash occurs, in other words get the compiler to tell me the conditions that made it crash the compilation?
>>> By debugging the compiler. Add OPT="-O- -gl" to add debug information and disable optimizations.
>>>
>> Isn't this just to add debugging information for using gdb?
> Mostly yes, that's why I answered "by debugging the compiler". The compiler has no logic built in to analyse why it crashes. And in your case, it seems even the stack is corrupt.
>
> Note that the AVR32 port is far from complete and probably still contains a multitude of bugs (even if you do get it to generate code, it's likely that it will be incorrect in many cases).
>
>
I am aware of that, but I need it to compile in order to fix the bugs. I had no problem compiling with the 2.6.0 tree. The compiler is created, it barfs when trying to create the RTL files.
It must be the new compiler that crashes. It looks like a game with gdb is needed.

For the compiler I updated the code to follow the changes in other processors so it would compile, there are quite a few changes between 2.6.0 and 2.7.1
As for the RTL the only changes I made was to add support for the processors that I have. The current code only had support for the uc3b1256 which isn't one that I have.



Michel


-- 
For Linux Software visit
http://home.comcast.net/~mcatudal




More information about the fpc-devel mailing list