This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/20644] RFE: valgrind interoperation with fortification
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 28 Sep 2016 11:16:19 +0000
- Subject: [Bug malloc/20644] RFE: valgrind interoperation with fortification
- Auto-submitted: auto-generated
- References: <bug-20644-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20644
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
(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
heap?
I thought that for stack allocations, valgrind has poor boundary information.
--
You are receiving this mail because:
You are on the CC list for the bug.