On Thu, 2016-02-04 at 08:54 +0100, Florian Krohm wrote: > On 03.02.2016 21:50, Philippe Waroquiers wrote: > > > > The assert might be caused by the debuginfo containing a string bigger > > than SEGINFO_STRPOOLSIZE (64Kb). > > Why exactly are we having yet another fixed size buffer here? > I've spent a lot of time crawling through the code and getting rid of > those. To read this is a bit of a disappointment. Yes, the work on removing or auditing the maxima was a nice thing. For this particular fixed size: This is not a (very) new fixed size buffer. It was already there at least in 3.9.0 (did not check before). In fact, I suspect that in 3.9.0, exceeding the maxima was causing a buffer overflow (i.e. was not checked).
I think it should not be that difficult to allow to exceed the pool size (but still keeping the pool size reasonable, and allocate a bigger one only when needed). Still, finding a 64kb string in the debug info is strange. 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
