public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "liaichun at huawei dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nss/26038] [core_dump] call getpwnam_r() appears core_dump
Date: Tue, 09 Jun 2020 08:29:05 +0000 [thread overview]
Message-ID: <bug-26038-131-GycQEH76op@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26038-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26038
--- Comment #10 from liaichun <liaichun at huawei dot com> ---
(In reply to Andreas Schwab from comment #9)
> nip should of course be a valid heap address or -1.
Sorry, i removed all my edits,and tried for a long time,it finally reappeared.
(gdb) p __pointer_chk_guard
$1 = 8256925845475092582
(gdb) p * __pointer_chk_guard
Cannot access memory at address 0x72967e4f3448e866
(gdb) p/x __pointer_chk_guard
$2 = 0x72967e4f3448e866
(gdb) bt
#0 0x72967e4f3448e866 in ?? ()
#1 0x0000ffff980683a4 in __getpwnam_r (name=0xffff984ca940 <g_logOwner>
"snasuser", resbuf=0xffff975be868, buffer=0xffff975be898 "", buflen=96,
result=0x0) at ../nss/getXXbyYY_r.c:315
#2 0x0000ffff983077d4 in __LOG_LogSetOwner (fd=7) at base_log.c:1778
#3 0x0000ffff98308cc0 in __LOG_Common_LogSelfTask (pArgv=0xffff991a1df8
<g_stLogUserAuditMgt>) at base_log.c:2588
#4 0x0000ffff992ee8bc in start_thread (arg=0xfffffcac7aff) at
pthread_create.c:486
#5 0x0000ffff980989dc in thread_start () at
../sysdeps/unix/sysv/linux/aarch64/clone.S:78
(gdb) info local
startp_initialized = true
startp = 0x7296d4e5ca99a906
start_fct = 0x729681b0a29137c6
nip = 0x72967e4f3448e866
do_merge = 0
mergegrp = <optimized out>
mergebuf = 0xffff9841a658 "V100R001C01"
endptr = 0x0
fct = {l = 0x72967e4f3448e866, ptr = 0x72967e4f3448e866}
no_more = 0
err = <optimized out>
status = NSS_STATUS_UNAVAIL
nscd_status = <optimized out>
res = <optimized out>
(gdb) exit
nip is 0x72967e4f3448e866 after PTR_DEMANGLE, so i guess nip is zero before
PTR_DEMANGLE?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-09 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 9:25 [Bug nss/26038] New: " liaichun at huawei dot com
2020-05-25 9:33 ` [Bug nss/26038] " liaichun at huawei dot com
2020-05-25 9:42 ` schwab@linux-m68k.org
2020-05-25 9:46 ` liaichun at huawei dot com
2020-05-25 9:52 ` schwab@linux-m68k.org
2020-05-25 10:00 ` liaichun at huawei dot com
2020-05-25 10:06 ` schwab@linux-m68k.org
2020-05-25 11:25 ` liaichun at huawei dot com
2020-05-25 12:20 ` schwab@linux-m68k.org
2020-05-25 12:29 ` schwab@linux-m68k.org
2020-06-09 8:29 ` liaichun at huawei dot com [this message]
2020-06-09 8:57 ` schwab@linux-m68k.org
2020-06-09 9:43 ` liaichun at huawei dot com
2020-08-05 13:57 ` liaichun at huawei dot com
2020-08-10 12:55 ` liaichun at huawei 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=bug-26038-131-GycQEH76op@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).