This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/20644] New: RFE: valgrind interoperation with fortification
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 28 Sep 2016 15:34:27 +0000
- Subject: [Bug malloc/20644] New: RFE: valgrind interoperation with fortification
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20644
Bug ID: 20644
Summary: RFE: valgrind interoperation with fortification
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: malloc
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: fweimer at redhat dot com, mjw at redhat dot com
Target Milestone: ---
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.
As it is, we get __fortify_fail() called, and a rough backtrace printed, and
maybe a program exit, but that's it. It would be better if, under valgrind, a
failing operation were actually attempted for valgrind to catch & report
nicely.
(Another possibility might be for valgrind to learn about all the _chk logic,
and emulate them internally. That seems like much more work.)
--
You are receiving this mail because:
You are on the CC list for the bug.