Re: Debugging

[James Colannino <james@colannino.org>]

Patrick Leslie Polzer wrote:

>First, define "does not function properly".  Does it dump code, is there a
>logic error?
>  
>

Sorry; I should have explained myself more clearly.  It's a logic error 
(I think.)  What's weird is that I ran strace to compare the various 
system calls used with the un-optimized version vs. the optimized 
version, and they were both the same up to the point where the optimized 
one failed.  Of course that isn't a reflection of the actual machine 
code, so I guess that wouldn't necessarily help me out too much.

>Then go about finding the offending line(s) of code.
>Watch out for obscure tricks, side-effects, wild pointers and illegal casts.
>Compile with -Wall and, to enforce your discipline, treat every warning as
>-Werror.
>  
>

Without -Wall, I get no errors (I always do my best to get rid of 
warnings.)  I'll try it with -Wall though and see what happens.

James

-- 
My blog: http://www.crazydrclaw.com/
My homepage: http://james.colannino.org/

"If Carpenters made houses the way programmers design programs, the first woodpecker to come along would destroy all of civilization." --Computer Proverb