On Thu, 2016-02-04 at 08:28 +0100, David Hallas wrote:
> Hi Philippe,
>
>
> thanks a lot for the quick reply!
>
>
> I have rerun the test with -v -v -v -d -d -d options and attached the
> log. I have also tested compiling the binary with gcc-5.2.1 and there
> I also see the problem, so it doesn't look to be compiler specific.
Strange thing is that there is no host stacktrace.
(so maybe the error is encountered before the debug info needed for
the stack trace is loaded).
>From the trace, if this is a (too) big string, then that string
is in gtest.
Maybe you could use objdump and/or other tools (strings?)
to find what could be this string of > 64Kb (if that is really the
problem).
>
>
> If you have some specific patches you want tested, I can pull the
> valgrind sources and do a local build?
Yes, what you could try is to increase
#define SEGINFO_STRPOOLSIZE (64*1024)
in coregrind/m_debuginfo/priv_storage.h
(e.g. to (640*1024))
and see if it works.
I would be nice also to add a
if (len > 64 * 1024)
VG_(printf("huge string <%s>\n", str);
in the ML_(addStr) function in storage.c
to understand what is this big string.
If the patch above and/or the printf do not give a clue; then
more debugging/tracing of valgrind will be needed.
Philippe
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
