--- In Andrew Taylor <> wrote:
>
> 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
>
Andrew,
(See my reply to Mark S from earlier today)
I tried compiling the sample I posted for Mark with the -O switch. It
compiled without giving me an error, but the program actually RUNS
without crashing! ANY of the "-O" switches seem to fix it!
Thanks for the tip.
Ed
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|