public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31256] Crash with basic 'list .'
Date: Tue, 23 Jan 2024 16:25:48 +0000	[thread overview]
Message-ID: <bug-31256-4717-zfUFIzz5YG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31256-4717@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The gdb-14-branch branch has been updated by Guinevere Larsen
<blarsen@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4fe1a40c7c464bde0212aa859774fe59fb71ccfe

commit 4fe1a40c7c464bde0212aa859774fe59fb71ccfe
Author: Guinevere Larsen <blarsen@redhat.com>
Date:   Mon Jan 22 10:13:52 2024 +0100

    gdb: fix "list ." related crash

    When a user attempts to use the "list ." command with an inferior that
    doesn't have debug symbols, GDB would crash. This was reported as PR
    gdb/31256.

    The crash would happen when attempting to get the current symtab_and_line
    for the stop location, because the symtab would return a null pointer
    and we'd attempt to dereference it to print the line.

    This commit fixes that by checking for an empty symtab and erroring out
    of the function if it happens.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31256
    Approved-By: Tom Tromey <tom@tromey.com>

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

  parent reply	other threads:[~2024-01-23 16:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  4:57 [Bug gdb/31256] New: [14 regression] " sam at gentoo dot org
2024-01-18 18:26 ` [Bug gdb/31256] " ssbssa at sourceware dot org
2024-01-18 18:39 ` sam at gentoo dot org
2024-01-18 19:43 ` csfore at posteo dot net
2024-01-18 22:33 ` csfore at posteo dot net
2024-01-19  8:44 ` [Bug gdb/31256] " blarsen at redhat dot com
2024-01-23 15:19 ` blarsen at redhat dot com
2024-01-23 15:43 ` csfore at posteo dot net
2024-01-23 15:59 ` cvs-commit at gcc dot gnu.org
2024-01-23 16:10 ` blarsen at redhat dot com
2024-01-23 16:25 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-11  4:42 ` brobecker at gnat dot com

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-31256-4717-zfUFIzz5YG@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).