|
From: Madhu M K. <mm...@ya...> - 2004-10-13 23:52:39
|
Hmm: On Wed, 2004-10-13 at 16:15, Bryan O'Sullivan wrote: > On Wed, 2004-10-13 at 23:04 +0200, Dennis Lubert wrote: > > _ZNSt8_Rb_treeIPKcSt4pairIKS1_SsESt10_Select1stIS4_EN5iwear12cstring_lessESaIS4_EE12insert_equalISt17_Rb_tree_iteratorIS4_RS4_PS4_EEEvT_SG_ > > Maybe valgrind is passing an insufficiently large buffer to > cplus_demangle? Using c++filt, this symbol expands to 1418 bytes. > Not sure if that is the cause as frequently I've had demangled entries cut off midway. Which is sort of a pet peeve of mine - I've had a bunch of times when I been forced to rebuild valgrind for different users who cant use the "default" build since the setting in question is far far too conservative (IMHO). coregrind/core.h: 124: /* Max length of a text fragment used to construct error messages. */ 125: #define M_VG_ERRTXT 512 Perhaps someone can answer to this question, but is there a reason why that shouldn't be something on the order of 2048? I did not believe this was "a bug" since users could work around it by rebuilding valgrind, but I can open one up...... Cheerio, M -- Madhu M Kurup /* Nemo Me Impune Lacessit */ mmk at yahoo-inc dt com |