public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gmx dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1970] getgrnam_r() and groups with more than 1024 bytes
Date: Fri, 09 Dec 2005 12:27:00 -0000 [thread overview]
Message-ID: <20051209122751.4066.qmail@sourceware.org> (raw)
In-Reply-To: <20051202172121.1970.burnus@gmx.de>
------- Additional Comments From burnus at gmx dot de 2005-12-09 12:27 -------
Created an attachment (id=789)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=789&action=view)
Test program, compile with g++ (uses "new")
I thought I attached the program here, but seemingly I didn't -- doing so now.
> > I get the crash only with compat, with file I also get ERANGE.
> So why did you wrote something complete different in the initial comment?
> "(independent of group:files vs. group:compat)".
Well, both is true:
Using getgrnam_r(name = "test", grp, buffer, bufsize=1024,result)
it only crashes with "group: compat". (Otherwise I get a ERANGE)
But using a buffer > 1024 it crashes with both group:compat and group:files
(stopping the nscd makes sense, otherwise the results can come from the cache,
I believe)
(gdb) run test
Starting program: /tmp/getent_test2 test
_SC_GETGR_R_SIZE_MAX = 1024
Call getgrnam_r(name = "test", grp, buffer, bufsize=2048,result)
Program received signal SIGSEGV, Segmentation fault.
0x4000b46a in fixup () from /lib/ld-linux.so.2
(gdb) bt
#0 0x4000b46a in fixup () from /lib/ld-linux.so.2
#1 0x4000b2c0 in _dl_runtime_resolve () from /lib/ld-linux.so.2
#2 0x4001cd54 in internal_endent () from /lib/libnss_files.so.2
#3 0x4001d0a2 in _nss_files_getgrnam_r () from /lib/libnss_files.so.2
#4 0x401c7354 in getgrnam_r@@GLIBC_2.1.2 () from /lib/tls/libc.so.6
#5 0x080485b4 in mygetgrnam_r (name=0xbfa390a9 "test", bufsize=2048) at
getent_test2.cpp:15
#6 0x08048628 in main (argc=2, argv=0xbfa376e4) at getent_test2.cpp:23
--
http://sourceware.org/bugzilla/show_bug.cgi?id=1970
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-12-09 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 17:21 [Bug libc/1970] New: " burnus at gmx dot de
2005-12-09 7:11 ` [Bug libc/1970] " kukuk at suse dot de
2005-12-09 11:53 ` burnus at gmx dot de
2005-12-09 12:00 ` burnus at gmx dot de
2005-12-09 12:01 ` kukuk at suse dot de
2005-12-09 12:27 ` burnus at gmx dot de [this message]
2005-12-30 20:52 ` drepper at redhat dot com
2006-04-23 19:47 ` drepper at redhat dot com
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=20051209122751.4066.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).