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 c++/31128] gdb crashes when trying to print a global variable stub without a running inferior
Date: Fri, 08 Dec 2023 18:10:23 +0000	[thread overview]
Message-ID: <bug-31128-4717-CnRllB2HCI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31128-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The gdb-14-branch branch has been updated by Hannes Domani
<ssbssa@sourceware.org>:

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

commit bc23ea51f8a83e9524dfb553baa8baacb29e68a9
Author: Hannes Domani <ssbssa@yahoo.de>
Date:   Fri Dec 8 19:06:14 2023 +0100

    Fix printing of global variable stubs if no inferior is running

    Since 3c45e9f915ae4aeab7312d6fc55a947859057572 gdb crashes when trying
    to print a global variable stub without a running inferior, because of
    a missing nullptr-check (the block_scope function took care of that
    check before it was converted to a method).

    With this check it works again:
    ```
    (gdb) print s
    $1 = <incomplete type>
    ```

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31128
    Approved-By: Tom Tromey <tom@tromey.com>
    (cherry picked from commit 576745e26c0ec76a53ba45b20af464628a50b3e4)

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

  parent reply	other threads:[~2023-12-08 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 18:03 [Bug c++/31128] New: " ssbssa at sourceware dot org
2023-12-08 18:08 ` [Bug c++/31128] " cvs-commit at gcc dot gnu.org
2023-12-08 18:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-08 18:11 ` ssbssa at sourceware dot org
2024-01-10 14:54 ` ssbssa at sourceware dot org
2024-03-29  8:00 ` wingo at igalia 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-31128-4717-CnRllB2HCI@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).