This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug malloc/20644] New: RFE: valgrind interoperation with fortification

            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

(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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]