public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30357] Segmentation fault for the 'start' command
Date: Sat, 15 Apr 2023 08:29:43 +0000	[thread overview]
Message-ID: <bug-30357-4717-Y7ppuoKdbh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30357-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30357

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-04-15

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Confirmed on openSUSE Tumbleweed, using:
...
gcc version 13.0.1 20230314 (experimental) [revision
42630fadbe248717859d61c0244c821c32b4e52c] (SUSE Linux) 
...

Happens here:
...
Thread 1 "gdb" received signal SIGSEGV, Segmentation fault.
0x000000000072cd38 in dwarf2_start_subfile (cu=0x2badc50, fe=..., lh=...) at
/data/vries/gdb/src/gdb/dwarf2/read.c:18716
18716     if (!IS_ABSOLUTE_PATH (filename) && dirname != NULL)
...
because:
...
(gdb) p filename
$1 = 0x0
...

It's probably triggered by an empty file name in the file name table:
...
 The File Name Table (offset 0x219, lines 2, columns 2):
  Entry Dir     Name
  0     0       (indirect line string, offset: 0x3c):
  1     0       (indirect line string, offset: 0x14d): test.c
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-04-15  8:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15  3:28 [Bug gdb/30357] New: " yangyibiao at nju dot edu.cn
2023-04-15  3:28 ` [Bug gdb/30357] " yangyibiao at nju dot edu.cn
2023-04-15  8:29 ` vries at gcc dot gnu.org [this message]
2023-04-16  6:34 ` vries at gcc dot gnu.org
2023-04-16 13:23 ` yangyibiao at nju dot edu.cn
2023-04-16 13:51 ` tromey at sourceware dot org
2023-04-17  8:25 ` [Bug symtab/30357] " vries at gcc dot gnu.org
2023-04-17  8:29 ` vries at gcc dot gnu.org
2023-04-17  8:36 ` vries at gcc dot gnu.org
2023-04-17  9:18 ` vries at gcc dot gnu.org
2023-04-17 16:09 ` cvs-commit at gcc dot gnu.org
2023-04-17 16:12 ` vries at gcc dot gnu.org
2023-04-18  3:47 ` cvs-commit at gcc dot gnu.org
2023-04-18  3:48 ` vries at gcc dot gnu.org

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=bug-30357-4717-Y7ppuoKdbh@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).