From: Mike Gulick <mike.gulick@mathworks.com>
To: gdb-patches@sourceware.org
Subject: [RFC][PATCH] fix gdb segv when objfile can't be opened
Date: Thu, 19 Oct 2017 14:10:00 -0000 [thread overview]
Message-ID: <59E8B251.4050100@mathworks.com> (raw)
This fixes PR 16577.
This patch changes gdb_bfd_map_section to issue a warning rather than an
error if it is unable to read the object file, and sets the size of the
section/frame that it attempted to read to 0 on error.
The description of gdb_bfd_map_section states that it will try to read
or map the contents of the section SECT, and if successful, the section
data is returned and *size is set to the size of the section data. This
function was throwing an error and leaving *size as-is. Setting the
section size to 0 indicates to dwarf2_build_frame_info that there is no
data to read, otherwise it will try to read from an invalid frame
pointer.
Changing the error to a warning allows this to be handled gracefully.
Additionally, the error was clobbering the breakpoint output indicating
the current frame (function name, arguments, source file, and line number).
E.g.
Thread 3 "foo" hit Breakpoint 1, BFD: reopening
/tmp/jna-1013829440/jna2973250704389291330.tmp: No such file or directory
BFD: reopening /tmp/jna-1013829440/jna2973250704389291330.tmp: No such
file or directory
(gdb)
While the "BFD: reopening ..." messages will still appear interspersed
in the
breakpoint output, the current frame info is now displayed:
Thread 3 "foo" hit Breakpoint 1, BFD: reopening
/tmp/jna-1013829440/jna1875755897659885075.tmp: No such file or directory
BFD: reopening /tmp/jna-1013829440/jna1875755897659885075.tmp: No such
file or directory
warning: Can't read data for section '.eh_frame' in file
'/tmp/jna-1013829440/jna1875755897659885075.tmp'
do_something () at file.cpp:80
80 {
(gdb)
---
gdb/gdb_bfd.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/gdb/gdb_bfd.c b/gdb/gdb_bfd.c
index 29080b8..229f5ae 100644
--- a/gdb/gdb_bfd.c
+++ b/gdb/gdb_bfd.c
@@ -705,9 +705,15 @@ gdb_bfd_map_section (asection *sectp, bfd_size_type
*size)
data = NULL;
if (!bfd_get_full_section_contents (abfd, sectp, &data))
- error (_("Can't read data for section '%s' in file '%s'"),
- bfd_get_section_name (abfd, sectp),
- bfd_get_filename (abfd));
+ {
+ warning (_("Can't read data for section '%s' in file '%s'"),
+ bfd_get_section_name (abfd, sectp),
+ bfd_get_filename (abfd));
+ /* Section is invalid -- set size to 0 and return NULL */
+ descriptor->size = 0;
+ *size = descriptor->size;
+ return (const gdb_byte *) NULL;
+ }
descriptor->data = data;
done:
--
2.1.4
next reply other threads:[~2017-10-19 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 14:10 Mike Gulick [this message]
2017-10-19 15:59 ` Mike Gulick
2017-10-19 17:54 ` Simon Marchi
2017-10-19 19:39 ` Mike Gulick
2017-10-19 20:10 ` Simon Marchi
2017-10-19 22:13 ` Mike Gulick
2017-10-23 23:19 ` Mike Gulick
2017-10-27 21:11 ` Simon Marchi
2017-10-28 1:19 ` Simon Marchi
2017-10-30 22:14 ` Mike Gulick
2017-10-30 23:38 ` Simon Marchi
2018-01-07 14:09 ` Simon Marchi
2018-01-08 0:45 ` Mike Gulick
2018-01-08 2:50 ` Simon Marchi
2018-01-08 2:51 ` Simon Marchi
2018-01-10 20:33 ` Mike Gulick
2018-01-12 2:44 ` Simon Marchi
2018-01-12 15:05 ` Mike Gulick
2018-01-17 18:01 ` Simon Marchi
2018-01-18 15:30 ` Mike Gulick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59E8B251.4050100@mathworks.com \
--to=mike.gulick@mathworks.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox