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 testsuite/25892] New: [debug-types] Testsuite FAILs
Date: Wed, 29 Apr 2020 07:48:02 +0000 [thread overview]
Message-ID: <bug-25892-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25892
Bug ID: 25892
Summary: [debug-types] Testsuite FAILs
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With:
- master,
- the tentative patch from PR25889 comment 2, and
- the submitted patch for PR25875 at
https://sourceware.org/pipermail/gdb-patches/2020-April/168011.html,
we have for target board debug-types:
...
FAIL: gdb.ada/info_auto_lang.exp: language_choice=auto: frame=0, frame_lang=c:
info types some_type
FAIL: gdb.ada/maint_with_ada.exp: maintenance check-psymtabs
FAIL: gdb.base/print-file-var.exp: lang=c: hidden=1: dlopen=0:
version_id_main=0: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c: hidden=1: dlopen=0:
version_id_main=1: sym1='print-file-var-lib1.c'::this_version_id,sym2=v1:
'print-file-var-lib1.c'::this_version_id == v1
FAIL: gdb.base/print-file-var.exp: lang=c: hidden=1: dlopen=0:
version_id_main=1: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c: hidden=1: dlopen=1:
version_id_main=0: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c: hidden=1: dlopen=1:
version_id_main=1: sym1='print-file-var-lib1.c'::this_version_id,sym2=v1:
'print-file-var-lib1.c'::this_version_id == v1
FAIL: gdb.base/print-file-var.exp: lang=c: hidden=1: dlopen=1:
version_id_main=1: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c++: hidden=1: dlopen=0:
version_id_main=0: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c++: hidden=1: dlopen=0:
version_id_main=1: sym1='print-file-var-lib1.c'::this_version_id,sym2=v1:
'print-file-var-lib1.c'::this_version_id == v1
FAIL: gdb.base/print-file-var.exp: lang=c++: hidden=1: dlopen=0:
version_id_main=1: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c++: hidden=1: dlopen=1:
version_id_main=0: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/print-file-var.exp: lang=c++: hidden=1: dlopen=1:
version_id_main=1: sym1='print-file-var-lib1.c'::this_version_id,sym2=v1:
'print-file-var-lib1.c'::this_version_id == v1
FAIL: gdb.base/print-file-var.exp: lang=c++: hidden=1: dlopen=1:
version_id_main=1: sym1='print-file-var-lib2.c'::this_version_id,sym2=v2:
'print-file-var-lib2.c'::this_version_id == v2
FAIL: gdb.base/setshow.exp: annotation_level 2 (timeout)
FAIL: gdb.base/setshow.exp: annotation_level 1
FAIL: gdb.base/volatile.exp: ptype victor
FAIL: gdb.base/volatile.exp: ptype victory
FAIL: gdb.base/volatile.exp: ptype cavern
FAIL: gdb.base/volatile.exp: ptype vizier
FAIL: gdb.base/volatile.exp: ptype cove
FAIL: gdb.base/volatile.exp: ptype cavity
FAIL: gdb.base/volatile.exp: ptype vagary
FAIL: gdb.base/volatile.exp: ptype vendor
FAIL: gdb.cp/local-static.exp: c++: print 'S::method() const volatile'
FAIL: gdb.cp/local-static.exp: c++: print 'S::method() volatile const'
FAIL: gdb.cp/local-static.exp: c++: print 'S::method(void) const volatile'
FAIL: gdb.cp/local-static.exp: c++: print S::method(void) const volatile
FAIL: gdb.cp/local-static.exp: c++: print 'S::method(void) volatile const'
FAIL: gdb.cp/local-static.exp: c++: print S::method(void) volatile const
FAIL: gdb.cp/method.exp: ptype A
FAIL: gdb.cp/no-dmgl-verbose.exp: setting breakpoint at 'f(std::string)'
FAIL: gdb.cp/oranking.exp: p foo15 (vc)
FAIL: gdb.cp/pass-by-ref-2.exp: call cbvFourCCtor (c1v1)
FAIL: gdb.cp/ptype-cv-cp.exp: ptype v_const_volatile_my_int
FAIL: gdb.guile/scm-symtab.exp: test simple_struct in static symbols
FAIL: gdb.python/lib-types.exp: python print (str
(const_volatile_class1_obj.type))
FAIL: gdb.python/py-symtab.exp: test simple_struct in static symbols
FAIL: gdb.python/py-xmethods.exp: before: g_size_diff 2
FAIL: gdb.python/py-xmethods.exp: before: g_size_mul 2
FAIL: gdb.python/py-xmethods.exp: before: g.mul<double>(2.0)
FAIL: gdb.python/py-xmethods.exp: before: g_mul 2
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
gdb compile failed, error: Unrecognized option: 'f'
=== gdb Summary ===
# of expected passes 78669
# of unexpected failures 42
# of expected failures 130
# of known failures 73
# of untested testcases 37
# of unsupported tests 83
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-29 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 7:48 vries at gcc dot gnu.org [this message]
2020-04-29 7:57 ` [Bug testsuite/25892] " vries at gcc dot gnu.org
2020-04-29 11:24 ` vries at gcc dot gnu.org
2020-04-30 13:24 ` 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-25892-4717@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).