On Wed, Dec 21, 2005 at 07:59:06PM +0100, Loïc Minier wrote: > On Wed, Dec 21, 2005, Steve Langasek wrote: > > All that will do is let you look at the value passed to strlen(); it won't > > tell you much about why it's wrong or where it came from.
> I imaginated it would help tracing a 64 bits -> 32-bits cast would that > be the problem here. Well, it may show you that this is the problem, but it won't really show you where it's happening if the guilty function isn't already in the backtrace. (I'm assuming we can rule out this being a libstdc++ or libc bug.) Also, aren't broken 64bit->32bit casts all fatal errors under gcc4? d4x has been built with gcc-4.0, as had gtk+2.0 2.6.10. > What do you suggest? valgrind? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
