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 mi/10347] gdb crashes with MI commands in hook-stop Date: Wed, 31 Aug 2022 17:15:17 +0000 [thread overview] Message-ID: <bug-10347-4717-Lj6ArfpXJx@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10347-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=10347 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=058dc2c95935d54caa8891613a1080d57665fc43 commit 058dc2c95935d54caa8891613a1080d57665fc43 Author: Tom Tromey <tromey@adacore.com> Date: Fri Aug 12 13:15:01 2022 -0600 Fix interpreter-exec crash PR mi/10347 points out that using interpreter-exec inside of a "define" command will crash gdb. The bug here is that gdb_setup_readline doesn't check for the case where instream==nullptr. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=10347 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-31 17:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10347-4717@http.sourceware.org/bugzilla/> 2022-08-12 19:16 ` tromey at sourceware dot org 2022-08-12 19:51 ` tromey at sourceware dot org 2022-08-31 17:15 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-31 17:15 ` tromey at sourceware dot org 2009-06-30 11:02 [Bug tdep/10347] New: " andre dot poenitz at nokia dot com 2009-06-30 13:04 ` [Bug mi/10347] " pedro at codesourcery dot com 2009-07-22 17:06 ` marc dot khouzam at ericsson 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-10347-4717-Lj6ArfpXJx@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).