public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sourceware at lancelotsix dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27133] Crash with set logging redirect and debugredirect Date: Wed, 13 Jan 2021 12:11:42 +0000 [thread overview] Message-ID: <bug-27133-4717-8Rje4pvLGY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27133-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27133 Lancelot SIX <sourceware at lancelotsix dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sourceware at lancelotsix dot com --- Comment #1 from Lancelot SIX <sourceware at lancelotsix dot com> --- Created attachment 13118 --> https://sourceware.org/bugzilla/attachment.cgi?id=13118&action=edit Patch to fix the issue Hi, This comes dowm to a use after delete problem. The attach patch has been proposed to gdb-patches@. I cannot assign myself to the bug so I mainly attach this patch so no-one spends time investigating on this problem. Multiple implementations are possible to solve this problem, none entirely satisfactory to my taste. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-13 12:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-31 7:08 [Bug gdb/27133] New: " nate at thatsmathematics dot com 2020-12-31 7:09 ` [Bug gdb/27133] " nate at thatsmathematics dot com 2021-01-13 12:11 ` sourceware at lancelotsix dot com [this message] 2021-01-27 22:16 ` cvs-commit at gcc dot gnu.org 2021-01-28 13:56 ` tromey at sourceware dot org
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-27133-4717-8Rje4pvLGY@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).