On Wednesday 12 November 2008, gaofeng37258 wrote: > Hi, > I'm a beginner of callgrind and try to use it.Now I meet a problem at > profile my application program by callgrind. > Callgrind exits soon after startup because of assertion fail.But i can run my > program normally without callgrind. Why?
This is a bug in callgrind about an unexpected mismatch of a signal number. It would be good if you create a bug report for it. For a chance to fix it, the best would be for me to be able to reproduce the problem. Can you try to make a small test case out of it? If this is out of questions, perhaps debug output can help. Run with valgrind --tool=callgrind --ct-verbose=2 --ct-vstart=xxx ncsim ... &> debug.log The xxx is some kind of time slot where to start with debug output. This should be as close to the error position as possible, as it slows down the process a lot. > 0x00028900 > BB# 127309796 > > Callgrind: threads.c:247 (vgCallgrind_post_signal): Assertion 'sigNum == > vgCallgrind_current_state.sig' failed. The xxx of your error is at line BB#, ie. 127309796. Because of nondetermism, you should use a value a little bit before, perhaps xxx=125000000. For the output, which is expected in the 10MB up to 1GB size, I just would need the last 1000 lines or something (with debug output for entering the signal handler which was left in the failed assertion). If the debug output is not enough, one can raise the output by using up to "--ct-verbose=9"... Cheers, Josef ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
