Nikos Mavrogiannopoulos <n...@gnutls.org> writes: > On 10/25/2011 01:25 PM, Simon Josefsson wrote: >> "Nikos Mavrogiannopoulos" <n...@gnutls.org> writes: >> >>> use coding.c from libtasn1 git, to avoid issue when compiled with >>> gcc-4.6. >> >> Hi Nikos! What's the issue? (maybe it hates strcat?) Should I do a >> new libtasn1 release with the fix? > > It looks like a gcc issue. I've reported it at: > http://lists.debian.org/debian-gcc/2011/08/msg00192.html
I wonder if that's not the same strlen bug I've seen sometimes: https://bugzilla.redhat.com/show_bug.cgi?id=678518#c2 Possibly strcat does a strlen internally, which results in the optimized strlen behaviour reading out of bounds that triggers valgrind. > The fix is a work around, however given that there is no fix for gcc in > debian, a new libtasn1 that doesn't have this issue would be best. There is some gnulib fixes in there too, and maybe I can find some other minor issue to fix as well.... so I can make another release. /Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org