From: Richard Earnshaw <rearnsha@arm.com>
To: gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: testsuite problems
Date: Fri, 08 Feb 2002 08:28:00 -0000 [thread overview]
Message-ID: <200202081628.QAA04564@cam-mail2.cambridge.arm.com> (raw)
I'm currently seeing the following when running the testsuite.
Running /nfs/sun18/work/rearnsha/gnusrc/src/gdb/src/gdb/testsuite/gdb.base/
corefile.exp ...
failed to get controlling terminal using TIOCSCTTYparent: sync byte write:
broken pipe
However, it only occurs if I'm running the whole suite. If I just run
corefile.exp it completes ok.
I seem to remember something like this once before (on another testsuite);
IIRC it occurs when a connection to a child isn't shut down cleanly after
a test (normally because the test failed in some way); the controlling pty
isn't released cleanly and we then eventually run out of ptys. Could this
be the problem here? -- certainly I'm seeing rather a large number of
failures at the moment, since I'm in the middle of trying to raise the ARM
code to multi-arch 1.
R.
next reply other threads:[~2002-02-08 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 8:28 Richard Earnshaw [this message]
2002-02-08 8:47 ` Andrew Cagney
2002-02-08 8:57 ` Richard Earnshaw
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=200202081628.QAA04564@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
/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