public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/31128] New: gdb crashes when trying to print a global variable stub without a running inferior Date: Fri, 08 Dec 2023 18:03:34 +0000 [thread overview] Message-ID: <bug-31128-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31128 Bug ID: 31128 Summary: gdb crashes when trying to print a global variable stub without a running inferior Product: gdb Version: 14.1 Status: NEW Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: ssbssa at sourceware dot org Target Milestone: --- It can be reproduced with this source: ``` struct S { S (int); virtual ~S (); int m_i; }; S s (5); int main () { return 0; } ``` And then just debugging the compiled object file: ``` $ g++ -g -c print-global-stub.cc $ gdb -q print-global-stub.o Reading symbols from print-global-stub.o... (gdb) p s This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ``` -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-12-08 18:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-08 18:03 ssbssa at sourceware dot org [this message] 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 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@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: linkBe 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).