aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/ChangeLog
diff options
context:
space:
mode:
authorFrank Ch. Eigler <fche@redhat.com>2019-08-06 11:23:48 -0400
committerFrank Ch. Eigler <fche@redhat.com>2019-08-06 15:09:53 -0400
commit404f29021abaef86a341663444fb069eb1f0282a (patch)
tree76a3409f363d27b2c0fcceaaea2dcf2a86f7e5e6 /gdb/testsuite/ChangeLog
parent046bebe1c0a367687bd693eb4594fcdcba0b8f7e (diff)
downloadgdb-404f29021abaef86a341663444fb069eb1f0282a.zip
gdb-404f29021abaef86a341663444fb069eb1f0282a.tar.gz
gdb-404f29021abaef86a341663444fb069eb1f0282a.tar.bz2
[PR build/24886] disable glibc mcheck support
This patch drops gdb's configury support for glibc's mcheck function. It has been observed to cause false abort()s, because it is thread-unsafe yet interposes every malloc/free operation. So if any library transitively used by gdb also uses threads, then these functions can easily corrupt their own checking data. These days, gcc ASAN and valgrind provide high quality checking, and mcheck is apparently itself being slowly deprecated. So, let's stop linking to it. Attached patch drops the autoconf/Makefile machinery for both gdb and gdbserver. No testsuite-visible impact. IMHO not worth mentioning in NEWS. See also: https://sourceware.org/bugzilla/show_bug.cgi?id=9939 gdb/ChangeLog PR build/24886 * configure.ac: Drop enable-libmcheck support. * configure, config.in: Rebuild. * libmcheck.m4: Remove. * acinclude.m4: Don't include it. * Makefile.in: Don't distribute it. * top.c (print_gdb_configuration): Don't mention it. gdb/gdbserver/ChangeLog PR build/24886 * configure.ac: Drop enable-libmcheck support. * configure, config.in: Rebuild. * acinclude.m4: Don't include it.
Diffstat (limited to 'gdb/testsuite/ChangeLog')
0 files changed, 0 insertions, 0 deletions