Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Hahnfeld, Jonas" <Hahnfeld@itc.rwth-aachen.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "qiyao@gcc.gnu.org" <qiyao@gcc.gnu.org>
Subject: [PATCH] Fix PR gdb/19208 - SIGSEV while opening Fortran program compiled with ifort
Date: Mon, 04 Jan 2016 15:47:00 -0000	[thread overview]
Message-ID: <233e961324084b0f857047bcf637c655@rwthex-s2-b.rwth-ad.de> (raw)

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

Hi all,

Find attached a patch that fixes a SIGSEV for me when trying to open a
Fortran program compiled with ifort (using version 16.0.1.150).
The error can be reproduced with a most simple file only containing "end"
and no additional compiler flags.

---
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 3d8923b..5890f78 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2016-01-04  Jonas Hahnfeld  <Hahnfeld@itc.rwth-aachen.de>
+
+       * dwarf2read.c (read_partial_die): Fix PR gdb/19208 -
+       SIGSEV while opening Fortran program compiled with ifort
+
 2016-01-04  Markus Metzger  <markus.t.metzger@intel.com>
 
        * btrace.c (btrace_pt_readmem_callback): Do not return in TRY/CATCH.
diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index c410500..1020c12 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -15936,7 +15936,8 @@ read_partial_die (const struct die_reader_specs
*reader,
             compilers pick up the new representation, we'll support this
             practice.  */
          if (DW_UNSND (&attr) == DW_CC_program
-             && cu->language == language_fortran)
+             && cu->language == language_fortran
+             && part_die->name != NULL)
            set_objfile_main_name (objfile, part_die->name,
language_fortran);
          break;
        case DW_AT_inline:

--
Jonas Hahnfeld, MATSE-Auszubildender

IT Center
Group: High Performance Computing
Division: Computational Science and Engineering
RWTH Aachen University
Seffenter Weg 23
D 52074  Aachen (Germany)
Hahnfeld@itc.rwth-aachen.de
www.itc.rwth-aachen.de


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5868 bytes --]

             reply	other threads:[~2016-01-04 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 15:47 Hahnfeld, Jonas [this message]
2016-01-06  6:20 ` Joel Brobecker
2016-01-06  7:42   ` Hahnfeld, Jonas
2016-01-14  7:19   ` Hahnfeld, Jonas
2016-01-17  6:18     ` Joel Brobecker

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=233e961324084b0f857047bcf637c655@rwthex-s2-b.rwth-ad.de \
    --to=hahnfeld@itc.rwth-aachen.de \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyao@gcc.gnu.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