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 at around 4100
>> characters (slightly less than that). That is not much of a problem per se,
>> but it means I do not know where the error is reported to be (the file+line
>> number combination is missing). Any idea where the error message length is
>> specified? I am using memcheck and the newest stable Valgrind 3.7.0.
>
> 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 do_cxx_demangling, Bool do_z_demangling,
Char* orig, Char* result, Int result_size )
{
# define N_ZBUF 4096
HChar* demangled = NULL;
HChar z_demangled[N_ZBUF];
If you increase N_ZBUF does it fix your problem?
Florian
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
