public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29965] [gdb] FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp: iteration=1: continue (the program exited)
Date: Thu, 05 Jan 2023 13:25:11 +0000	[thread overview]
Message-ID: <bug-29965-4717-76D3v41nCx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29965-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> with a revert of
> commit cb25fdbb76e ("gdb: remove assertion in
> psymbol_functions::expand_symtabs_matching") which I expect should not
> matter.

Confirmed, FAILs also reproduce without the revert, so with clean trunk.

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

  parent reply	other threads:[~2023-01-05 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 12:30 [Bug gdb/29965] New: " vries at gcc dot gnu.org
2023-01-05 12:30 ` [Bug gdb/29965] " vries at gcc dot gnu.org
2023-01-05 12:36 ` vries at gcc dot gnu.org
2023-01-05 12:37 ` vries at gcc dot gnu.org
2023-01-05 12:50 ` vries at gcc dot gnu.org
2023-01-05 12:56 ` vries at gcc dot gnu.org
2023-01-05 13:14 ` vries at gcc dot gnu.org
2023-01-05 13:25 ` vries at gcc dot gnu.org [this message]
2023-01-06 11:21 ` vries at gcc dot gnu.org
2023-06-22 13:45 ` iii at linux dot ibm.com
2023-09-12 17:57 ` simon.marchi at polymtl dot ca
2023-09-26 18:21 ` cvs-commit at gcc dot gnu.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-29965-4717-76D3v41nCx@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).