public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug remote/26614] AddressSanitizer: heap-use-after-free of extended_remote_target in remote_async_inferior_event_handler Date: Sun, 29 Nov 2020 15:15:35 +0000 [thread overview] Message-ID: <bug-26614-4717-hOQH3un8Ei@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26614-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26614 --- Comment #13 from Simon Marchi <simark at simark dot ca> --- If that's indeed the problem, I can see two solutions: 1. Have some kind of listener that the function can install locally to get notified if the target gets destroyed, and skip the following code if so. 2. That code exists to re-mark the async event handler if we still have things to report, because it is automatically cleared by check_async_event_handlers. Instead, we can make check_async_event_handlers leave the async event handler marked and let the target clear it in its ::wait implementation when it no longer has anything to report. Or, as a stop-gap solution, have the remote_async_inferior_event_handler re-mark the handler before calling inferior_event_handler and clear it in ::wait if there's nothing else to report. I have a patch that does that (in the middle of a big work-in-progress series), as you can see it gets rid of the problematic code: https://review.lttng.org/c/binutils-gdb/+/4050/11 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-29 15:15 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-14 14:50 [Bug gdb/26614] New: UNRESOLVED: gdb.multi/multi-target.exp: continue: non-stop=on: inferior 5 vries at gcc dot gnu.org 2020-09-14 14:52 ` [Bug gdb/26614] " vries at gcc dot gnu.org 2020-09-14 14:52 ` vries at gcc dot gnu.org 2020-09-14 14:56 ` vries at gcc dot gnu.org 2020-09-14 15:14 ` vries at gcc dot gnu.org 2020-09-15 9:41 ` vries at gcc dot gnu.org 2020-09-15 9:42 ` vries at gcc dot gnu.org 2020-09-15 10:14 ` [Bug remote/26614] AddressSanitizer: heap-use-after-free of extended_remote_target in remote_async_inferior_event_handler vries at gcc dot gnu.org 2020-09-25 23:58 ` palves at redhat dot com 2020-09-29 13:25 ` vries at gcc dot gnu.org 2020-11-29 9:19 ` vries at gcc dot gnu.org 2020-11-29 10:20 ` vries at gcc dot gnu.org 2020-11-29 11:24 ` vries at gcc dot gnu.org 2020-11-29 14:53 ` simark at simark dot ca 2020-11-29 15:15 ` simark at simark dot ca [this message] 2020-11-30 10:32 ` vries at gcc dot gnu.org 2020-11-30 11:02 ` vries at gcc dot gnu.org 2020-11-30 12:06 ` vries at gcc dot gnu.org 2020-11-30 14:11 ` simark at simark dot ca 2020-11-30 14:35 ` vries at gcc dot gnu.org 2020-11-30 14:57 ` simark at simark dot ca 2020-11-30 15:00 ` palves at redhat dot com 2020-11-30 15:10 ` simark at simark dot ca 2021-01-07 12:27 ` vries at gcc dot gnu.org 2021-01-07 12:34 ` vries at gcc dot gnu.org 2021-01-07 13:40 ` vries at gcc dot gnu.org 2021-01-07 16:10 ` vries at gcc dot gnu.org 2021-01-07 20:41 ` cvs-commit at gcc dot gnu.org 2021-01-31 6:16 ` brobecker at gnat dot com 2021-01-31 6:58 ` vries at gcc dot gnu.org 2021-01-31 7:16 ` vries at gcc dot gnu.org 2021-02-04 18:43 ` simark at simark dot ca 2021-06-27 17:52 ` ahmedsayeed1982 at yahoo dot com 2021-08-10 11:45 ` ucelsanicin at yahoo dot com 2021-08-18 13:42 ` jamesrogan59 at gmail dot com 2021-08-19 5:53 ` ucelsanicin at yahoo dot com 2021-09-02 11:00 ` donipah907 at mtlcz dot com 2021-09-02 11:18 ` mark at klomp dot org 2021-09-06 9:09 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:40 ` mehmetgelisin at aol dot com 2021-09-14 17:29 ` johnb6174 at gmail dot com 2021-09-26 13:31 ` tes.vik1986 at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-17 19:48 ` vmireskazki at gmail dot com 2021-10-19 7:15 ` progonsaytu at gmail dot com 2021-10-23 13:46 ` fiteva5725 at bomoads dot com 2021-10-24 10:03 ` glassmtech at ukr dot net 2021-11-06 21:12 ` paneki8601 at dukeoo dot com 2021-11-10 14:11 ` bryanmcsp at gmail dot com 2021-11-13 19:31 ` tesaso8237 at funboxcn dot com 2021-11-16 11:05 ` mrsrvic at yahoo dot com 2021-11-16 19:04 ` xecana8007 at funboxcn dot com 2021-11-16 19:08 ` xecana8007 at funboxcn dot com 2021-11-16 19:12 ` xecana8007 at funboxcn dot com 2021-11-22 7:38 ` gexed96894 at keagenan 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-26614-4717-hOQH3un8Ei@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).