I've fixed this in revision 14673.
Curious, what GCC version have you been using?
I recommend you file a bug report in the future as issues reported on
the mailing list easily get forgotten.
Florian
On 18.09.2014 10:09, Matthias Apitz wrote:
>
> Hello,
>
> This is on a Linux host running:
>
Er, this isn't good. Can you file a bug report
as described at http://www.valgrind.org/support/bug_reports.html
so that this gets tracked properly? If it just remains on the mailing
list it is likely to get forgotten.
Thanks.
J
On 09/18/2014 10:09 AM, Matthias Apitz wrote:
>
> Hello,
>
> T
Hello,
This is on a Linux host running:
valgrind-3.10.0> uname -a
Linux SRAP03DXOH 2.6.5-7.191-bigsmp #1 SMP Tue Jun 28 14:58:56 UTC 2005 i686
athlon i386 GNU/Linux
valgrind-3.10.0> CFLAGS="-DPTRACE_GETSIGINFO=0x4202" export CFLAGS
valgrind-3.10.0> ./configure
valgrind-3.10.0> gmake
...
mv -f