Re: Conditional jump or move depends on uninitialised value(s)

On Wed, 2007-06-27 at 12:29 -0400, Jeffrey Stedfast wrote:

> as far as the other valgrind warnings... well, I can't help but wonder
> if this is actually a gcc optimization bug?

I think I'm agreeing with you on those. I investigated them a little
bit, and I saw very few possibilities how things can go wrong.

Though, I'll keep an eye om them. Who knows sooner or later we'll find
something suspicious?

The problem is that even very small memory problems cause a lot of havoc
on certain architectures (like ARM), where we are moving Camel to. So
I'm indeed going after all of them.


-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://www.pvanhoof.be/blog