From: Tom de Vries <tdevries@suse.de>
To: Guinevere Larsen <blarsen@redhat.com>,
Alex Chronopoulos <achronop@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v6] Change message when reaching end of reverse history.
Date: Tue, 27 Aug 2024 12:17:18 +0200 [thread overview]
Message-ID: <07bf3284-cdd7-4349-8e42-6d22931b3299@suse.de> (raw)
In-Reply-To: <18f1a5da-5581-4dcc-bdf3-2aaf2b161d31@redhat.com>
On 8/26/24 15:41, Guinevere Larsen wrote:
> Pushed :)
Hi Gwen,
After this patch got pushed, I ran into:
...
(gdb) PASS: gdb.btrace/non-stop.exp: no progress: all: thread apply all
continue: prompt
^M
Reached end of recorded history; stopping.^M
Following forward execution will be added to history.^M
test (arg=0x0) at
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/non-stop.c:30^M
30 return arg; /* bp.2 */^M
^M
Reached end of recorded history; stopping.^M
Following forward execution will be added to history.^M
test (arg=0x0) at
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/non-stop.c:30^M
30 return arg; /* bp.2 */^M
PASS: gdb.btrace/non-stop.exp: no progress: all: thread apply all
continue: thread 0
FAIL: gdb.btrace/non-stop.exp: no progress: all: thread apply all
continue: thread 1 (timeout)
...
I suppose the test-case needs to be updated.
Thanks,
- Tom
next prev parent reply other threads:[~2024-08-27 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 16:43 Alex Chronopoulos
2024-08-12 19:50 ` Guinevere Larsen
2024-08-13 8:52 ` Metzger, Markus T
2024-08-13 11:55 ` Guinevere Larsen
2024-08-13 18:18 ` Alex Chronopoulos
2024-08-13 18:26 ` Guinevere Larsen
2024-08-23 12:25 ` Alex Chronopoulos
2024-08-26 13:41 ` Guinevere Larsen
2024-08-27 10:17 ` Tom de Vries [this message]
2024-08-27 11:07 ` Guinevere Larsen
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=07bf3284-cdd7-4349-8e42-6d22931b3299@suse.de \
--to=tdevries@suse.de \
--cc=achronop@gmail.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@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