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/31435] New: [gdb/testsuite] Runtest error running DAP tests Date: Thu, 29 Feb 2024 12:58:11 +0000 [thread overview] Message-ID: <bug-31435-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31435 Bug ID: 31435 Summary: [gdb/testsuite] Runtest error running DAP tests 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: --- When running the following command: ... $ ( cd build/gdb/testsuite ; make V=1 check 'RUNTESTFLAGS=gdb.dap/ada-arrays.exp gdb.dap/ada-nested.exp gdb.dap/attach.exp' ) ... I run into: ... === gdb tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /data/vries/gdb/src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file. Running /data/vries/gdb/src/gdb/testsuite/gdb.dap/ada-nested.exp ... Running /data/vries/gdb/src/gdb/testsuite/gdb.dap/attach.exp ... Running /data/vries/gdb/src/gdb/testsuite/gdb.dap/ada-arrays.exp ... child process exited abnormally while executing "exec sh -c "exec > /dev/null 2>&1 && (kill -2 -$spid || kill -2 $spid)"" (procedure "close_wait_program" line 20) invoked from within "close_wait_program $shell_id $pid" (procedure "standard_close" line 23) invoked from within "standard_close "unix"" ("eval" body line 1) invoked from within "eval ${try}_${proc} \"$dest\" $args" (procedure "call_remote" line 42) invoked from within "call_remote "" close "$host"" (procedure "remote_close" line 3) invoked from within "remote_close target" (procedure "cleanup_target_hook" line 13) invoked from within "cleanup_target_hook $current_target" ("foreach" body line 283) invoked from within "foreach current_target $target_list { verbose "target is $current_target" set current_target_name $current_target set tlist [split $curren..." (file "/usr/share/dejagnu/runtest.exp" line 1619) make[1]: *** [Makefile:226: do-check-single] Error 1 make[1]: Leaving directory '/data/vries/gdb/leap-15-4/build/gdb/testsuite' make: *** [Makefile:161: check] Error 2 ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-29 12:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-29 12:58 vries at gcc dot gnu.org [this message] 2024-02-29 13:19 ` [Bug testsuite/31435] " vries at gcc dot gnu.org 2024-02-29 15:52 ` tromey at sourceware dot org 2024-03-14 16:37 ` tromey at sourceware dot org 2024-03-14 17:29 ` tromey at sourceware dot org 2024-03-14 17:57 ` tromey at sourceware dot org 2024-03-14 20:13 ` vries at gcc dot gnu.org 2024-03-15 9:15 ` vries at gcc dot gnu.org 2024-03-15 13:33 ` tromey at sourceware dot org 2024-03-15 13:38 ` tromey at sourceware dot org 2024-03-15 13:39 ` tromey at sourceware dot org 2024-03-15 14:30 ` tromey at sourceware dot org 2024-03-18 13:01 ` cvs-commit at gcc dot gnu.org 2024-03-18 13:02 ` tromey at sourceware dot 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-31435-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: linkBe 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).