aboutsummaryrefslogtreecommitdiff
path: root/gdb/python
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-12-20 12:51:50 +0000
committerAndrew Burgess <aburgess@redhat.com>2022-12-24 16:02:47 +0000
commit3a98808c164b36c7023bd80fc6b019cbe6274365 (patch)
treeacf86b5f4cac2c18f925bc9dfa0cc459e971269e /gdb/python
parentf5e82fac07c48dd72b44f7b11b866f59ec086815 (diff)
downloadgdb-3a98808c164b36c7023bd80fc6b019cbe6274365.zip
gdb-3a98808c164b36c7023bd80fc6b019cbe6274365.tar.gz
gdb-3a98808c164b36c7023bd80fc6b019cbe6274365.tar.bz2
gdb/testsuite: fix buffer overflow in gdb.base/signed-builtin-types.exp
In commit: commit 9f50fe0835850645bd8ea9bb1efe1fe6c48dfb12 Date: Wed Dec 7 15:55:25 2022 +0000 gdb/testsuite: new test for recent dwarf reader issue A new test (gdb.base/signed-builtin-types.exp) was added that made use of 'info sources' to figure out if the debug information for a particular object file had been fully expanded or not. Unfortunately some lines of the 'info sources' output can be very long, this was observed on some systems where the debug information for the dynamic-linker was installed, in this case, the list of source files associated with the dynamic linker was so long it would cause expect's internal buffer to overflow. This commit switches from using 'info sources' to 'maint print objfile', the output from the latter command is more compact, but also, can be restricted to a single named object file. With this change in place I am no longer seeing buffer overflow errors from expect when running gdb.base/signed-builtin-types.exp.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions