> However, I had gone to great lengths to insert symbol information into my > image in order to chase down a run time issue I am having with the code. > Therefore, while running with --demangle=no is a good experiment, it is not > a practical option for me.
Why? You can always postprocess output with c++filt to recover the original C++ names. > Turning callgrind on interactively is not a valid option since I am chasing > a run time crash You are trying to chase down a crash? Wouldn't --tool=memcheck be a more suitable tool for that? If you can use memcheck, then you can send all its output to a network socket using the --log-socket option, so there will be no need to write a log file. J ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
