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 breakpoints/21497] FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed
Date: Mon, 14 Aug 2023 20:39:13 +0000	[thread overview]
Message-ID: <bug-21497-4717-KGInmvS7Df@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21497-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by John Baldwin <jhb@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a6f51542941e072d942fc8df7353bd10097974ea

commit a6f51542941e072d942fc8df7353bd10097974ea
Author: John Baldwin <jhb@FreeBSD.org>
Date:   Mon Aug 14 13:38:42 2023 -0700

    fbsd-nat: Defer any ineligible events reported by wait.

    If wait_1 finds an event for a thread or process that does not match
    the set of threads and processes previously resumed, defer the event.
    If the event is for a specific thread, suspend the thread and continue
    the associated process before waiting for another event.

    One specific example of such an event is if a thread is created while
    another thread in the same process hits a breakpoint.  If the second
    thread's event is reported first, the target resume method does not
    yet "know" about the new thread and will not suspend it via
    PT_SUSPEND.  When wait is called, it will probably return the event
    from the first thread before the result of the step from second
    thread.  This is the case reported in PR 21497.

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

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

  parent reply	other threads:[~2023-08-14 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21497-4717@http.sourceware.org/bugzilla/>
2022-11-25 16:23 ` morrand276 at gmail dot com
2022-11-29 20:26 ` tromey at sourceware dot org
2023-08-14 20:39 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-08 18:57 ` ssbssa at sourceware dot org
2024-01-08 21:21 ` jhb at FreeBSD 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-21497-4717-KGInmvS7Df@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).