|
From: <gil...@ya...> - 2004-04-10 18:30:07
|
> > The above was obtained with --num-callers=20. Any > > ideas what could be lurking at 0x8F? > > Stack-walking is not always reliable, I think > Valgrind's getting confused > here, and wouldn't pay too much attention to the > 0x8f. Try with > --run-libc-freeres=no. If you don't get an error, > then I think it shows > that the problem is with glibc -- libc-freeres is a > glibc routine that > frees up all glibc's memory. There is no error with --run-libc-freeres=no. I guess that solves that one then. That said, why does glibc have this problem? ____________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html |