On 03/02/2012 06:39 AM, Julian Seward wrote:
On Friday, March 02, 2012, SFBay Area wrote:
Hi,
I have started coding in C++ and use a lot of templates, and I do mean a
lot. Unfortunately, my type names became way too long for Valgrind to
handle. Currently, it seems that it cuts the type name
It might be BUF_LEN defined in VG_(describe_IP) in
coregrind/m_debuginfo/debuginfo.c, currently 4096.
Alternatively you can use --demangle=no and demangle
the output by hand by pushing it through c++filt.
There is also a hard-coded limit here:
void VG_(demangle) ( Bool
Regarding that demangled name exceeding line length, I found all files
in coregrid/ that defined a buffer with length 4096 and changed them
all to 32768, now Valgrind works fine. I guess the buffers you guys
suggested went through a smaller buffer at some point, getting cut
short. Would it be a
Hi,
I have started coding in C++ and use a lot of templates, and I do mean a
lot. Unfortunately, my type names became way too long for Valgrind to
handle. Currently, it seems that it cuts the type name at around 4100
characters (slightly less than that). That is not much of a problem per se,
but
On Friday, March 02, 2012, SFBay Area wrote:
Hi,
I have started coding in C++ and use a lot of templates, and I do mean a
lot. Unfortunately, my type names became way too long for Valgrind to
handle. Currently, it seems that it cuts the type name at around 4100
characters (slightly less
