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 guile/26533] FAIL: gdb.guile/scm-type.exp: lang_c: test_fields: cast to array with two arguments
Date: Mon, 14 Sep 2020 06:11:25 +0000 [thread overview]
Message-ID: <bug-26533-4717-E2g0d3IS7g@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26533-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26533
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #9)
> (In reply to Ludovic Courtès from comment #8)
> > I tried running the tests under 'rr'
>
> Is that https://rr-project.org/ ?
>
> > but that seems to prevent GDB from
> > spawning the inferior or something:
> >
> > FAIL: gdb.guile/scm-type.exp: can't run to main
> >
> > Is there a trick to achieve that?
>
> Can you show how you tried this?
OK, I managed, using:
...
@@ -1895,6 +1895,8 @@ proc gdb_file_cmd { arg } {
}
}
+set GDB "rr $GDB"
+
# Default gdb_spawn procedure.
proc default_gdb_spawn { } {
...
Then, I made it clear we're running into a timeout:
...
@@ -689,7 +689,7 @@ proc runto { function args } {
# If you don't want that, use gdb_start_cmd.
proc runto_main { } {
- return [runto main no-message]
+ return [runto main message]
}
### Continue, and expect to hit a breakpoint.
...
such that we get:
...
FAIL: gdb.guile/scm-type.exp: running to main in runto (timeout)
FAIL: gdb.guile/scm-type.exp: can't run to main
...
I've then tried to increase the timeout to:
...
@@ -632,7 +632,7 @@ proc runto { function args } {
# the "at foo.c:36" output we get with -g.
# the "in func" output we get without -g.
- gdb_expect 30 {
+ gdb_expect 600 {
-re "Break.* at .*:$decimal.*$gdb_prompt $" {
if { $print_pass } {
pass $test_name
...
but I haven't found a value yet that works.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-14 6:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:31 [Bug guile/26533] New: " vries at gcc dot gnu.org
2020-08-25 10:32 ` [Bug guile/26533] " vries at gcc dot gnu.org
2020-08-25 11:34 ` vries at gcc dot gnu.org
2020-08-25 11:41 ` vries at gcc dot gnu.org
2020-08-25 14:45 ` vries at gcc dot gnu.org
2020-08-25 14:48 ` vries at gcc dot gnu.org
2020-09-13 14:14 ` ludo at gnu dot org
2020-09-13 14:18 ` ludo at gnu dot org
2020-09-13 20:42 ` ludo at gnu dot org
2020-09-14 4:27 ` vries at gcc dot gnu.org
2020-09-14 6:11 ` vries at gcc dot gnu.org [this message]
2021-05-18 10:24 ` vries at gcc dot gnu.org
2021-05-18 10:26 ` 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-26533-4717-E2g0d3IS7g@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).