aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-07-28 06:25:11 -0600
committerTom Tromey <tromey@adacore.com>2023-07-31 08:22:45 -0600
commitf717822dd7b07c8b1cb92a19bc4778bd9c967116 (patch)
tree44ad4f741bf780ed24c4efdb9c2e6eec81257f01
parent5b512234c874d5f82734dc6115765bc691c2c982 (diff)
downloadgdb-f717822dd7b07c8b1cb92a19bc4778bd9c967116.zip
gdb-f717822dd7b07c8b1cb92a19bc4778bd9c967116.tar.gz
gdb-f717822dd7b07c8b1cb92a19bc4778bd9c967116.tar.bz2
Set PYTHONMALLOC in the test suite
Setting PYTHONMALLOC helped me locate an earlier bug. It seems to me that there aren't big downsides to always setting this during testing, and it might help find other bugs in the future.
-rw-r--r--gdb/testsuite/lib/gdb.exp4
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 66c04a2..12a9c59 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -6437,6 +6437,10 @@ proc default_gdb_init { test_file_name } {
# tests.
setenv TERM "dumb"
+ # This setting helps detect bugs in the Python code and doesn't
+ # seem to have a significant downside for the tests.
+ setenv PYTHONMALLOC malloc_debug
+
# If DEBUGINFOD_URLS is set, gdb will try to download sources and
# debug info for f.i. system libraries. Prevent this.
if { [is_remote host] } {