public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28942] Problem with breakpoint condition calling a function in multi-threaded program
Date: Fri, 04 Mar 2022 14:01:08 +0000	[thread overview]
Message-ID: <bug-28942-4717-9HRbsFxIQT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28942-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28942

--- Comment #2 from Andrew Burgess <aburgess at redhat dot com> ---
Created attachment 14005
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14005&action=edit
A WIP patch

Here's the patch I'm currently working on.  This should apply to current master
and resolves the issue in this bug, as well as the original issue I was working
on.  I've run the complete testsuite on GNU/Linux x86-64 with no regressions.

I still need to do lots more testing, especially around things like handling
targets that don't support non-stop mode, and what happens if some other thread
stops while we are evaluating the breakpoint condition.

But any initial thoughts are welcome.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-03-04 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 19:40 [Bug gdb/28942] New: " simon.marchi at polymtl dot ca
2022-03-04 11:15 ` [Bug gdb/28942] " aburgess at redhat dot com
2022-03-04 14:01 ` aburgess at redhat dot com [this message]
2022-03-04 14:44 ` simark at simark dot ca
2022-03-07  7:34 ` tankut.baris.aktemur at intel dot com
2022-10-21 17:57 ` tromey at sourceware dot org
2022-10-21 17:57 ` tromey at sourceware dot org
2022-10-21 17:58 ` tromey at sourceware dot org
2024-03-25 17:40 ` cvs-commit at gcc dot gnu.org
2024-07-02 16:34 ` ssbssa 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-28942-4717-9HRbsFxIQT@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: link
Be 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).