|
From: | Andrew Hutchinson |
Subject: | [avr-gcc-list] GCC Testing |
Date: | Tue, 15 Jan 2008 20:53:53 -0500 |
User-agent: | Thunderbird 2.0.0.9 (Windows/20071031) |
I found real bug in testing setup. Now I have correct libc, it is returning from main ok and calling exit.However, exit and abort are defined is testsuite exit.c as naked function. Yet code tries to place exit code non-existent frame and it crashes stack. This happens mostly when tests have optimisation -O0 (as other levels would tend to remove frame)
I have no idea why we would need them to be naked. They are only used as simulator breakpoints. Likely it was not seen before as simulavr didn't squawk about the bad access.
My code is now: void exit (int code); /*__attribute__ ((naked));*/ void exit(int code) { exit_code = code; if (code==0) abort(); for (;;); } void abort (void); /* __attribute__ ((naked));*/ void abort (void) { application_aborted = 1; for (;;); } Weddington, Eric wrote:
-----Original Message-----From: Paulo Marques [mailto:address@hidden Sent: Tuesday, January 15, 2008 5:01 PMTo: address@hiddenCc: Weddington, Eric; Andrew Hutchinson; address@hidden; address@hidden; KlausRudolph Subject: RE: Simulator for GCC Testing [was: RE: [Fwd: Re:[avr-gcc-list]GCC-AVR Register optimisations]]Quoting William Rivet <address@hidden>:I still didn't look into it, but my idea was to host in place that gave the idea of "this is what you need to run the gcc testsuite for gcc" and not so much "this is where you can find yet another avr simulator". I was just trying to make it work myself before thinking about an official release.BTW: Where would you host your new tool?FWIW, I'm willing to host it on the WinAVR CVS repository. Thanks, Eric Weddington
[Prev in Thread] | Current Thread | [Next in Thread] |