On Thursday 17 June 2010, Satya V. Gupta wrote: > Since you asked, I ran Valgrind with --demangle=no; the SIGSEGV issue I saw > earlier went away.
Very good. > 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. I have the exact same question as Julian here: what is your problem with "--demangle=no"? It does not cut down any functionality. Symbols will just show up demangled, which you can cope with in a postprocessing step afterwards. > Is there another way in valgrind to restrict the > string size offered to VG_(strcmp)() so that it won't crash? Can there be > canary protection around the valgrind stack to protect it from being overrun > in situations like these? For practical reasons, this seems next to impossible for me. Josef ------------------------------------------------------------------------------ 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
