public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pronovic at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/9077] gij is unable to run some programs in the NBIO test suite
Date: Sun, 02 Nov 2003 23:43:00 -0000	[thread overview]
Message-ID: <20031102234328.26357.qmail@sources.redhat.com> (raw)
In-Reply-To: <20021228030601.9077.172031@bugs.debian.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9077



------- Additional Comments From pronovic at debian dot org  2003-11-02 23:43 -------
After talking with the Debian maintainer, I have come up with a smaller test
case that I hope will be easier to use.  The test case is attached as
testcase.tar.gz, which I'll attach after I add this comment.  The .tar.gz file
contains a README file explaining what's in the resulting directory.  Basically,
I've stripped down the NBIO source code to two classes and a JNI function which
reproduces the behavior.  I don't know a lot about JNI, so I can't claim that
the code is correct, only that it compiles and that the Kaffe and Blackdown JVMs
can run it with no problems.  The problem appears to be with the definition of
the java.net.DatagramPacket object.


  parent reply	other threads:[~2003-11-02 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021228030601.9077.172031@bugs.debian.org>
2003-07-21 18:00 ` pinskia at physics dot uc dot edu
2003-10-06 19:54 ` pinskia at gcc dot gnu dot org
2003-11-02  0:18 ` pronovic at debian dot org
2003-11-02 23:43 ` pronovic at debian dot org [this message]
2003-11-02 23:46 ` pinskia at gcc dot gnu dot org
2003-11-03  2:34 ` pinskia at gcc dot gnu dot org

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=20031102234328.26357.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).