|
From: Christoph B. <bar...@or...> - 2005-09-28 21:36:54
|
> > You shouldn't ignore it as it means that the preload library won't > have been injected into the client. I think the only effect of that > is to stop the C library resources being freed on exit though. > > There is obviously something badly wrong however as it looks like > you are trying to valgrind a 32 bit program with a 64 bit valgrind > except that you shouldn't be able to do that - it should complain > and exit if you try as that doesn't work. > > Presumably this is a 64 bit machine - how exactly did you configure > valgrind? Did you intend it to be a 32 or 64 bit valgrind? I am trying to valgrind a 64bit program on a 64bit machine. However this programm forks off bzip2 to compress a log file it writes out. bzip2 is 32bit on this machine. 64bit valgrind cannot analyse 32bit applications right now. That's why the main program is not run with --trace-children=yes. Christoph |