Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com, alexander.v.shaposhnikov@gmail.com
Subject: [gdb patch] seg fault on missing dwarf
Date: Mon, 25 Sep 2017 20:33:00 -0000	[thread overview]
Message-ID: <02efda56-3678-f4f6-849d-df474214e82f@acm.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 512 bytes --]

Pedro,
this is Alex's patch of 
https://sourceware.org/ml/gdb-patches/2017-09/msg00745.html cleaned up 
with changelog formatting.  Alex is a fellow FaceBooker.

The patch looks obvious to me, particularly as a few lines down we have:

       fprintf_unfiltered (gdb_stdlog,
			  "    %s CUs, %s TUs\n",
			  pulongest (dwp_file->cus ? dwp_file->cus->nr_units : 0),
			  pulongest (dwp_file->tus ? dwp_file->tus->nr_units : 0));

to protect dump output from exactly this problem.

ok?

nathan
-- 
Nathan Sidwell

[-- Attachment #2: gdb-null.diff --]
[-- Type: text/x-patch, Size: 1171 bytes --]

2017-09-25  Alexander Shaposhnikov <alexander.v.shaposhnikov@gmail.com>
	
	* dwarf2read.c (open_and_init_dwp_file): Protect against dwp_file
	having NULL cus or tus.

diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index b1914cf..547e3f0 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -11185,7 +11185,8 @@ open_and_init_dwp_file (void)
   dwp_file->tus = create_dwp_hash_table (dwp_file, 1);
 
   /* The DWP file version is stored in the hash table.  Oh well.  */
-  if (dwp_file->cus->version != dwp_file->tus->version)
+  if (dwp_file->cus && dwp_file->tus
+      && dwp_file->cus->version != dwp_file->tus->version)
     {
       /* Technically speaking, we should try to limp along, but this is
 	 pretty bizarre.  We use pulongest here because that's the established
@@ -11195,7 +11196,7 @@ open_and_init_dwp_file (void)
 	     pulongest (dwp_file->cus->version),
 	     pulongest (dwp_file->tus->version), dwp_name.c_str ());
     }
-  dwp_file->version = dwp_file->cus->version;
+  dwp_file->version = dwp_file->cus ? dwp_file->cus->version : 0;
 
   if (dwp_file->version == 2)
     bfd_map_over_sections (dwp_file->dbfd, dwarf2_locate_v2_dwp_sections,

             reply	other threads:[~2017-09-25 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 20:33 Nathan Sidwell [this message]
2017-09-26 14:27 ` Pedro Alves
2017-09-26 23:05   ` Nathan Sidwell
2017-09-26 23:12     ` Alexander Shaposhnikov

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=02efda56-3678-f4f6-849d-df474214e82f@acm.org \
    --to=nathan@acm.org \
    --cc=alexander.v.shaposhnikov@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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