public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/31352] [gdb/cli, recursive internal problem] sig_write uses gdb_stderr, which may be a string_file, which doesn't support write_async_safe Date: Thu, 11 Apr 2024 19:06:07 +0000 [thread overview] Message-ID: <bug-31352-4717-4Q393GmzaC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31352-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31352 Guinevere Larsen <blarsen at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blarsen at redhat dot com --- Comment #1 from Guinevere Larsen <blarsen at redhat dot com> --- I've come across this same bug while trying to debug a segfault from my frame_unwind move to classes[1] on 32-bit arm, no changes required to internal_vproblem or quit function. If you stop inside frame_unwind_legacy::sniffer and send a segfault to inner GDB, you can trigger the situation where internal_verror is writing to a gdb_stderr that doesn't have write_async_safe. [1] https://inbox.sourceware.org/gdb-patches/20240408201915.1482831-4-blarsen@redhat.com/T/#u -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-11 19:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-07 13:50 [Bug cli/31352] New: [gdb/cli, recursive internal problem] sig_write uses gdb_stderr->write_async_safe, which may be a string_file vries at gcc dot gnu.org 2024-02-07 13:51 ` [Bug cli/31352] [gdb/cli, recursive internal problem] sig_write uses gdb_stderr, which may be a string_file, which doesn't support write_async_safe vries at gcc dot gnu.org 2024-04-11 19:06 ` blarsen at redhat dot com [this message] 2024-04-12 20:11 ` blarsen at redhat 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-31352-4717-4Q393GmzaC@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).