public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: georg.denk@infineon.com
To: gcc-gnats@gcc.gnu.org
Subject: libgcj/10186: Static binary aborts if netgroups are used
Date: Fri, 21 Mar 2003 16:56:00 -0000 [thread overview]
Message-ID: <20030321165037.6870.qmail@sources.redhat.com> (raw)
>Number: 10186
>Category: libgcj
>Synopsis: Static binary aborts if netgroups are used
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 21 16:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Denk Georg
>Release: gcc version 3.2.2
>Organization:
>Environment:
RedHat 7.2
Linux host 2.4.18-26.7.xsmp #1 SMP Mon Feb 24 09:18:30 EST 2003 i686 unknown
rpm says glibc-2.2.4-32
>Description:
After compiling a java file into a static binary, this binary
aborts if /etc/nsswitch.conf contains "passwd: compat"
and /etc/passwd does not include the user directly but
via NIS netgroup.
If either the nsswitch.conf entry is changed to
"passwd: files nis" or the user is a local user in /etc/passwd, the binary runs at it should. Non-static binaries work in both situations. In the real application it was sufficient to exclude libc from being linked statically.
>How-To-Repeat:
See attached file
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="out"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="out"
dXNlckBob3N0OiB+L2phdmEgJSBjYXQgRmlib25hY2NpLmphdmEKY2xhc3MgRmlib25hY2NpCnsK
ICBzdGF0aWMgZmluYWwgaW50IGxpbWl0ID0gNTA7CgogIHB1YmxpYyBzdGF0aWMgdm9pZCBtYWlu
IChTdHJpbmcgW10gYXJncykKICAgewogICAgIGludCBsb3cgID0gMTsKICAgICBpbnQgaGlnaCA9
IDE7CgogICAgIFN5c3RlbS5vdXQucHJpbnRsbigiRmlib25hY2NpIHZhbHVlcyB1cCB0byAiICsg
bGltaXQpOyAgCiAgICAgU3lzdGVtLm91dC5wcmludGxuKGxvdyk7IAoKICAgICB3aGlsZSAoIGhp
Z2ggPCBsaW1pdCApCiAgICAgIHsKICAgICAgICBTeXN0ZW0ub3V0LnByaW50bG4gKCBoaWdoICk7
CiAgICAgICAgaGlnaCA9IGhpZ2ggKyBsb3c7CiAgICAgICAgbG93ICA9IGhpZ2ggLSBsb3c7CiAg
ICAgIH0KICAgfQp9Cgp1c2VyQGhvc3Q6IH4vamF2YSAlIC9zdy9nY2MzL2Jpbi9nY2ogLXYKUmVh
ZGluZyBzcGVjcyBmcm9tIC9zdy9nY2MzL2xpYi9nY2MtbGliL2k2ODYtcGMtbGludXgtZ251LzMu
Mi4yL3NwZWNzClJlYWRpbmcgc3BlY3MgZnJvbSAvc3cvZ2NjMy9saWIvZ2NjLWxpYi9pNjg2LXBj
LWxpbnV4LWdudS8zLjIuMi8uLi8uLi8uLi9saWJnY2ouc3BlYwpyZW5hbWUgc3BlYyBsaWIgdG8g
bGlib3JpZwpDb25maWd1cmVkIHdpdGg6IC4vY29uZmlndXJlIC0tcHJlZml4PS9zdy9nY2MzIC0t
d2l0aC1sb2NhbC1wcmVmaXg9L3N3L2xvY2FsClRocmVhZCBtb2RlbDogcG9zaXgKZ2NjIHZlcnNp
b24gMy4yLjIKCnVzZXJAaG9zdDogfi9qYXZhICUgL3N3L2djYzMvYmluL2djaiAtYyBGaWJvbmFj
Y2kuamF2YQoKdXNlckBob3N0OiB+L2phdmEgJSAvc3cvZ2NjMy9iaW4vZ2NqIC1zdGF0aWMgLW8g
Rmlib25hY2NpIC0tbWFpbj1GaWJvbmFjY2kgRmlib25hY2NpLm8KCnVzZXJAaG9zdDogfi9qYXZh
ICUgLi9GaWJvbmFjY2kKQWJvcnQK
reply other threads:[~2003-03-21 16:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030321165037.6870.qmail@sources.redhat.com \
--to=georg.denk@infineon.com \
--cc=gcc-gnats@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).