public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/21941] NPE in Socket.connect() Date: Thu, 20 Apr 2006 15:46:00 -0000 [thread overview] Message-ID: <20060420154655.13672.qmail@sourceware.org> (raw) In-Reply-To: <bug-21941-360@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from tromey at gcc dot gnu dot org 2006-04-20 15:46 ------- Subject: Bug 21941 Author: tromey Date: Thu Apr 20 15:46:40 2006 New Revision: 113118 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113118 Log: PR libgcj/21941: * gnu/java/net/natPlainDatagramSocketImplPosix.cc (send): Throw UnknownHostException if needed. * gnu/java/net/natPlainSocketImplPosix.cc (connect): Throw UnknownHostException if needed. Modified: trunk/libjava/ChangeLog trunk/libjava/gnu/java/net/natPlainDatagramSocketImplPosix.cc trunk/libjava/gnu/java/net/natPlainSocketImplPosix.cc -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21941
next prev parent reply other threads:[~2006-04-20 15:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-21941-360@http.gcc.gnu.org/bugzilla/> 2006-04-20 15:42 ` tromey at gcc dot gnu dot org 2006-04-20 15:46 ` tromey at gcc dot gnu dot org [this message] 2006-04-20 15:47 ` tromey 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=20060420154655.13672.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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: linkBe 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).