Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* testsuite problems
@ 2002-02-08  8:28 Richard Earnshaw
  2002-02-08  8:47 ` Andrew Cagney
  0 siblings, 1 reply; 3+ messages in thread
From: Richard Earnshaw @ 2002-02-08  8:28 UTC (permalink / raw)
  To: gdb; +Cc: Richard.Earnshaw


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.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: testsuite problems
  2002-02-08  8:28 testsuite problems Richard Earnshaw
@ 2002-02-08  8:47 ` Andrew Cagney
  2002-02-08  8:57   ` Richard Earnshaw
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Cagney @ 2002-02-08  8:47 UTC (permalink / raw)
  To: Richard.Earnshaw; +Cc: gdb

> 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


BSD?


> 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.


I don't know, could well be.  I've seen the message on FreeBSD and 
NetBSD systems and never been able to track it down - re-running the 
testsuite made it disappear :-(

Andrew


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: testsuite problems
  2002-02-08  8:47 ` Andrew Cagney
@ 2002-02-08  8:57   ` Richard Earnshaw
  0 siblings, 0 replies; 3+ messages in thread
From: Richard Earnshaw @ 2002-02-08  8:57 UTC (permalink / raw)
  To: Andrew Cagney; +Cc: Richard.Earnshaw, gdb

> > failed to get controlling terminal using TIOCSCTTYparent: sync byte write: 
> > broken pipe
> 
> 
> BSD?
> 

Yep. (NetBSD)

> I've seen the message on FreeBSD and  NetBSD systems and never been
> able to track it down - re-running the  testsuite made it disappear
> :-( 

Hmm, well my shark has a fairly limited number of ptys (64), so with 
200-odd failures by that point, it is plausible.

R.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-02-08 16:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-08  8:28 testsuite problems Richard Earnshaw
2002-02-08  8:47 ` Andrew Cagney
2002-02-08  8:57   ` Richard Earnshaw

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox