To: | |
---|---|
Subject: | Re: [ts-7000] Segmentation Fault - I blame it on gcc's linker |
From: | Andrew Taylor <> |
Date: | Fri, 3 Aug 2007 16:52:05 +1000 |
A bit more debugging advice. Its better to run "gcc -O -Wall". This detects (some) use of uninitalized local variables which "gcc -Wall" does not - I assume because some flow analysis is not done without -O. Even better is to follow Don Carr's advice and use stubs for hardware-specific code and compile and test on x86 where you can use valgrind and gcc -fmudflap to pick useful classes of bugs automatically. Andrew |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [ts-7000] Segmentation Fault - I blame it on gcc's linker, mark_s |
---|---|
Next by Date: | Re: [ts-7000] Re: java recommendations, justin |
Previous by Thread: | Re: [ts-7000] Segmentation Fault - I blame it on gcc's linker, mark_s |
Next by Thread: | [ts-7000] Re: Segmentation Fault - I blame it on gcc's linker, Ed |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU