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/29962] FAIL: gdb.reverse/step-reverse.exp: reverse step into fn call
Date: Wed, 11 Jan 2023 10:08:14 +0000 [thread overview]
Message-ID: <bug-29962-4717-Tp4OjP6X2G@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29962-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29962
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 14576
--> https://sourceware.org/bugzilla/attachment.cgi?id=14576&action=edit
log file including debug infrun output (gcc 12.2.1 case)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-11 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 10:09 [Bug gdb/29962] New: " vries at gcc dot gnu.org
2023-01-04 13:30 ` [Bug gdb/29962] " vries at gcc dot gnu.org
2023-01-04 17:18 ` vries at gcc dot gnu.org
2023-01-11 9:39 ` vries at gcc dot gnu.org
2023-01-11 10:03 ` vries at gcc dot gnu.org
2023-01-11 10:06 ` vries at gcc dot gnu.org
2023-01-11 10:08 ` vries at gcc dot gnu.org [this message]
2023-01-12 11:55 ` vries at gcc dot gnu.org
2023-01-12 16:30 ` vries 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-29962-4717-Tp4OjP6X2G@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).