aboutsummaryrefslogtreecommitdiff
path: root/gdb/compile
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2019-01-21 08:41:28 -0700
committerTom Tromey <tom@tromey.com>2019-01-21 09:05:01 -0700
commitd7167c671da0323daf31a8e07945c57c25f858d2 (patch)
treef51aa2a375d4c9bbeb38df4941b41a0579793682 /gdb/compile
parent73021deb50855f31bb312241899a464c62155f6a (diff)
downloadgdb-d7167c671da0323daf31a8e07945c57c25f858d2.zip
gdb-d7167c671da0323daf31a8e07945c57c25f858d2.tar.gz
gdb-d7167c671da0323daf31a8e07945c57c25f858d2.tar.bz2
Fix leak in splay-tree
Philippe Waroquiers noticed a memory leak in gdb, which he tracked down to a bug in splay-tree. splay_tree_remove does not call the `delete_key' function when it removes the old node; but it should. I looked at every splay tree in GCC and there is only one that passes a non-NULL delete function -- the one in lto.c. That file does not call splay_tree_remove. So, I think this is safe to check in. I re-ran the LTO tests to double check. libiberty/ * splay-tree.c (splay_tree_remove): Delete the key if necessary.
Diffstat (limited to 'gdb/compile')
0 files changed, 0 insertions, 0 deletions