This is the mail archive of the
mailing list for the glibc project.
[Bug malloc/20644] RFE: valgrind interoperation with fortification
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 29 Sep 2016 09:29:46 +0000
- Subject: [Bug malloc/20644] RFE: valgrind interoperation with fortification
- Auto-submitted: auto-generated
- References: <firstname.lastname@example.org/bugzilla/>
--- Comment #2 from Mark Wielaard <mjw at redhat dot com> ---
(In reply to Florian Weimer from comment #1)
> (In reply to Frank Ch. Eigler from comment #0)
> > It would be handy if glibc could detect that it is running under valgrind
> > (see RUNNING_ON_VALGRIND in /usr/include/valgrind.h) when running its
> > fortify checks. valgrind can produce higher quality error messages than
> > glibc for errors, but only if valgrind sees the erroneous string/buffer ops.
> Is this unconditionally true, or does this apply only if buffers are on the
> I thought that for stack allocations, valgrind has poor boundary information.
memcheck does not perform bounds checking for stack (or global arrays).
It does track stack size and definedness of stack values.
You are receiving this mail because:
You are on the CC list for the bug.