From: Tom Tromey <tromey@redhat.com>
To: Austin Gonyou <austin@coremetrics.com>
Cc: eclipse@sources.redhat.com
Subject: Re: EPIC Plugin make Eclipse crazy.
Date: Tue, 05 Aug 2003 20:31:00 -0000 [thread overview]
Message-ID: <87he4vetua.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1060106982.3658.2.camel@portageek.digitalroadkill.net>
>>>>> "Austin" == Austin Gonyou <austin@coremetrics.com> writes:
Austin> java.io.IOException: Interrupted system call
Austin> at java.io.FileDescriptor.read(byte[], int, int)
I think this is a libgcj bug. We saw something similar with the RPM
plugin. The fix didn't make the cut for this release.
It is fixed in the gcc cvs repository though. You want to find this
patch:
2003-07-25 Tom Tromey <tromey@redhat.com>
* java/io/natFileDescriptorPosix.cc (write): Try again on EINTR.
(write): Likewise.
(read): Likewise.
(read): Likewise.
Tom
prev parent reply other threads:[~2003-08-05 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 18:25 Austin Gonyou
2003-08-05 20:31 ` Austin Gonyou
2003-08-05 20:45 ` Tom Tromey
2003-08-11 16:05 ` Austin Gonyou
2003-08-12 21:41 ` Tom Tromey
2003-08-05 20:31 ` Tom Tromey [this message]
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=87he4vetua.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=austin@coremetrics.com \
--cc=eclipse@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).