From: Jim Wilson <jimw@sifive.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 8.2.90 available for testing
Date: Wed, 27 Feb 2019 22:05:00 -0000 [thread overview]
Message-ID: <332e186f-0c04-ab6d-754e-bf14d2981923@sifive.com> (raw)
In-Reply-To: <20190227055112.4A5E782D7B@joel.gnat.com>
On 2/26/19 9:51 PM, Joel Brobecker wrote:
> I have just finished creating the gdb-8.2.90 pre-release.
> Please give it a test if you can and report any problems you might find.
On a riscv64-linux system (HiFive Unleashed w/ Fedora Core 29), without
an Ada compiler in my path, I get
=== gdb Summary ===
# of expected passes 50264
# of unexpected failures 2297
# of expected failures 57
# of unknown successes 3
# of known failures 79
# of untested testcases 132
# of unresolved testcases 110
# of unsupported tests 359
which looks OK. There was no riscv-linux native support in gdb-8.2 so
this is a major improvement over the last one. I did used to have
better results though. I'm seeing
hifiveu017:1040$ grep ^FAIL gdb.sum | grep infcall | wc
878 8059 103059
and I think that these mostly used to work, since I used to have about
1500 failures. I think something in the last 3 months broke this, but I
haven't had time to track it down. I see stuff like this in the log files
p/d check_arg_struct_01_01 (ref_val_struct_01_01)^M
../../binutils-gdb/gdb/riscv-tdep.c:2119: internal-error: void
riscv_call_arg_struct(riscv_arg_info*, riscv_call_info*): Assertion
`TYPE_LENGTH (ainfo->type) == TYPE_LENGTH (sinfo.field_type (0))' failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
Quit this debugging session? (y or n) FAIL:
gdb.base/infcall-nested-structs.exp: l=c++: types-tfc: p/d
check_arg_struct_01_01 (ref_val_struct_01_01) (GDB internal error)
Jim
next prev parent reply other threads:[~2019-02-27 22:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 5:51 Joel Brobecker
2019-02-27 22:05 ` Jim Wilson [this message]
2019-03-04 11:15 ` Andrew Burgess
2019-03-04 13:57 ` Alan Hayward
2019-03-04 20:00 ` Jim Wilson
2019-02-28 18:31 ` MinGW build of GDB 8.2.90 (was: GDB 8.2.90 available for testing) Eli Zaretskii
2019-02-28 18:55 ` MinGW build of GDB 8.2.90 Sergio Durigan Junior
2019-02-28 19:06 ` LRN
2019-02-28 19:45 ` Eli Zaretskii
2019-02-28 20:17 ` Sergio Durigan Junior
2019-02-28 20:29 ` Eli Zaretskii
2019-02-28 20:37 ` Sergio Durigan Junior
2019-02-28 18:34 ` GDB 8.2.90 available for testing Eli Zaretskii
2019-03-01 16:35 ` Pedro Alves
2019-03-01 18:50 ` Tom Tromey
2019-03-07 22:44 ` Tom Tromey
2019-03-08 7:46 ` Eli Zaretskii
2019-03-08 20:57 ` Tom Tromey
2019-03-09 6:13 ` Eli Zaretskii
2019-03-14 17:32 ` Tom Tromey
2019-03-14 19:49 ` Eli Zaretskii
2019-03-15 12:55 ` Tom Tromey
2019-03-17 15:56 ` Eli Zaretskii
2019-03-17 17:31 ` Tom Tromey
2019-03-17 18:36 ` Eli Zaretskii
2019-03-18 14:13 ` Tom Tromey
2019-03-18 18:08 ` Eli Zaretskii
2019-03-07 17:42 ` Pedro Franco de Carvalho
[not found] ` <4d855905-32ce-ba4b-72f5-037f1796b37e@redhat.com>
2019-03-22 14:42 ` [PATCH] Fix testsuite hangs when gdb_test_multiple body errors out (Re: GDB 8.2.90 available for testing) Simon Marchi
2019-03-25 13:23 ` Pedro Alves
2019-03-22 20:44 ` Pedro Franco de Carvalho
2019-03-25 13:21 ` Pedro Alves
2019-03-25 19:43 ` Pedro Franco de Carvalho
2019-03-26 18:58 ` Pedro Alves
2019-03-26 21:01 ` Pedro Franco de Carvalho
2019-03-28 17:36 ` Joel Brobecker
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=332e186f-0c04-ab6d-754e-bf14d2981923@sifive.com \
--to=jimw@sifive.com \
--cc=brobecker@adacore.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