public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "greenrd at greenrd dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/17069] New: InetAddress.getLocalHost() returns broken InetAddress object if hostname not set Date: Tue, 17 Aug 2004 20:33:00 -0000 [thread overview] Message-ID: <20040817203326.17069.greenrd@greenrd.org> (raw) On Linux, if the hostname of the localhost has not been set, the hostname command-line utility returns "(none)" (which is an invalid hostname, obviously). In this situation, a call to getLocalHost() will return an InetAddress object with a null addr field, which will cause getAddress() and other methods to throw a NPE. Expected behaviour: A more indicative exception would be useful. From the API docs, getLocalHost() should throw an java.net.UnknownHostException if it cannot determine an IP address for the local host. However, I'm not sure that last resort would ever be necessary. Wouldn't 127.0.0.1 for both IP address and hostname be a failsafe fallback, for as long as IPv4 is around? -- Summary: InetAddress.getLocalHost() returns broken InetAddress object if hostname not set Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: minor Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: greenrd at greenrd dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17069
next reply other threads:[~2004-08-17 20:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-17 20:33 greenrd at greenrd dot org [this message] 2005-01-07 22:40 ` [Bug libgcj/17069] " konqueror at gmx dot de 2005-01-09 18:57 ` cvs-commit at gcc dot gnu dot org 2005-01-09 18:59 ` 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=20040817203326.17069.greenrd@greenrd.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).