aboutsummaryrefslogtreecommitdiff
path: root/gdb/thread.c
diff options
context:
space:
mode:
authorMarkus Metzger <markus.t.metzger@intel.com>2014-05-22 08:47:42 +0200
committerMarkus Metzger <markus.t.metzger@intel.com>2014-06-25 09:54:31 +0200
commit1d1f1ccb331f1fe9825c3bb6f6231a3aeb560d6f (patch)
tree873d0ea4e5a1045e06bbbce37ef9e3f8ce54c0f3 /gdb/thread.c
parent31f0c4c1c653b59ce8552402ecc1b3249273f2de (diff)
downloadgdb-1d1f1ccb331f1fe9825c3bb6f6231a3aeb560d6f.zip
gdb-1d1f1ccb331f1fe9825c3bb6f6231a3aeb560d6f.tar.gz
gdb-1d1f1ccb331f1fe9825c3bb6f6231a3aeb560d6f.tar.bz2
make_corefile_notes: have caller free returned memory
The various make_corefile_notes implementations for gdbarch as well as target currently make an xfree cleanup on the data they return. This causes problems when trying to put a TRY_CATCH around the make_corefile_notes call. Specifically, we get a stale cleanup error in restore_my_cleanups. Omit the make_cleanup and have the caller free the memory. gdb/ * fbsd-nat.c (fbsd_make_corefile_notes): Remove make_cleanup call. * gcore.c (write_gcore_file): Free memory returned from make_corefile_notes. * linux-tdep.c (linux_make_corefile_notes): Remove make_cleanup call. * procfs.c (procfs_make_note_section): Remove make_cleanup call.
Diffstat (limited to 'gdb/thread.c')
0 files changed, 0 insertions, 0 deletions