From: Kevin Buettner <kevinb@redhat.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Skip gdb.base/libsegfault.exp on Cygwin
Date: Wed, 11 Jun 2025 10:43:12 -0700 [thread overview]
Message-ID: <20250611104312.3ada6f06@f41-zbm-amd> (raw)
In-Reply-To: <20250606174648.982691-1-pedro@palves.net>
On Fri, 6 Jun 2025 18:46:48 +0100
Pedro Alves <pedro@palves.net> wrote:
> Running gdb.base/libsegfault.exp on Cygwin, in parallel mode causes
> badness:
>
> $ make check-parallel TESTS="gdb.base/libsegfault.exp"
> ...
> Running /home/alves/gdb/src/gdb/testsuite/gdb.base/libsegfault.exp ...
> 0 [main] expect 6611 C:\cygwin64\bin\expect.exe: *** fatal error in forked process - error while loading shared libraries: libSegFault.so: cannot open shared object file: No such file or directory
> *** starting '"C:\cygwin64\bin\dumper.exe" -n "C:\cygwin64\bin\expect.exe" 8012' for pid 6611, tid 7992
> *** continuing pid 6611
> parent: sync byte write: broken pipe
> make[1]: *** [Makefile:320: check/gdb.base/libsegfault.exp] Error 255
> make[1]: Target 'do-check-parallel' not remade because of errors.
> make[1]: Leaving directory '/home/alves/rocm/gdb/build-cygwin-testsuite'
> outputs/gdb.base/libsegfault/gdb.sum: no recognised summary line
> outputs/gdb.base/libsegfault/gdb.log: no recognised summary line
> make: *** [Makefile:260: check-parallel] Error 2
> $
>
> I.e., Expect's spawn fails, and that brings down the whole Expect
> process, for some reason. The result is that we end up with
> incomplete gdb.sum/gdb.log files, which dg-extract-results.sh can't
> process. Since libSegFault.so is a glibc feature that doesn't exist
> on Cygwin, just skip the test there.
>
> Change-Id: I44bdbffa25a5d21c5019418b68776d334a57be26
LGTM.
Approved-by: Kevin Buettner <kevinb@redhat.com>
next prev parent reply other threads:[~2025-06-11 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 17:46 Pedro Alves
2025-06-11 17:43 ` Kevin Buettner [this message]
2025-09-23 9:48 ` [pushed v2] " Pedro Alves
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=20250611104312.3ada6f06@f41-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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