From: Nicholas N. <nj...@ca...> - 2003-05-27 16:09:13
|
On 27 May 2003, Hong Chen wrote: > I'm using valgrind to detect leaks in my program without any luck. When > I start valgrind : > valgrind -v myapp args > > it worked fine at the very beginning, but when it tried to load a shared > object , following error messages showed up : > > ==2684== Jump to the invalid address stated on the next line > ==2684== at 0x0: ??? > ==2684== Address 0x0 is not stack'd, malloc'd or free'd > Segmentation fault > > Without valgrind, I haven't get any trouble to run myapp. Could anyone > give me a pointer ? any input would be appreciated. That's the message you have a variable that is uninitialised, and then you try to jump to the "address" stored in that variable. But since your program works fine normally, I'd guess it's a Valgrind bug. Can you provide the full output from running with -v? Better still, can you trim down your program into a small example that triggers the error? Thanks. N |