libgcj/1430: Writing on OutputStream of bad Socket kills app with "Broken pipe"

[John Griffin]

The following reply was made to PR libgcj/1430; it has been noted by GNATS.

From: John Griffin <john@ndr.com>
To: gcc-gnats@gcc.gnu.org, tromey@gcc.gnu.org
Cc:  
Subject: Re: libgcj/1430: Writing on OutputStream of bad Socket kills app with "Broken pipe"
Date: Thu, 21 Dec 2000 15:29:43 -0500 (EST)

 In reference to libgcj/1430 and 1425, I don't know what in the world 
 happened, but either our sendmail or yours went nolstagic.  I sent and 
 you responded and fixed these well more than a year ago.
 
 Anyway, if it's my end, accept apologies for the annoyance and ignore 
 these reports.
 
 
 John C. Griffin, 
 Ned Davis Research, Inc.
 
 On 20 Dec 2000 gcc-gnats@gcc.gnu.org wrote:
 
 > Thank you very much for your problem report.
 > It has the internal identification `libgcj/1430'.
 > The individual assigned to look at your
 > report is: tromey. 
 > 
 > >Category:       libgcj
 > >Responsible:    tromey
 > >Synopsis:       Writing on OutputStream of bad Socket kills app with "Broken pipe"
 > >Arrival-Date:   Wed Dec 20 12:19:46 PST 2000
 >