|
From: Jeremy F. <je...@go...> - 2003-11-07 17:18:15
|
On Thu, 2003-11-06 at 08:08, Dhirendra Pal Singh wrote: > Hi All, > I am new to this valgrind. I am trying to valgrind my code. Its a pretty > decent size code with lot of multithreading. Now when I start valgrind > using the following command... > > valgrind --num-callers=20 --alignment=8 --leak-check=yes > --leak-resolution=med --error-limit=no --show-reachable=yes > /usr/sbin/myprog > > It shows me some error messages in the beginig, and then goes to sleep. > By sleep I mean that the process dosent dies but dosent do anything > either... It shows 0.0 percent cpu usage, and does not respond to key > stroke. > [...] > Now I tried to attach gdb/totalview to it this myprog while valgrinding. > And it shows the myprog is stuck at line 2154 of vg_scheduler.c .. > the code is as follows... It's probably blocked in a syscall. What does strace -p <pid> show? Attaching with gdb/totalview is more likely to be confusing than useful, since your program isn't even really running when it's under Valgrind. BTW, the message it prints is probably a real bug, so you should look at fixing that first. J |