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: Mon, 25 May 2020 10:00:39 +0000	[thread overview]
Message-ID: <bug-26038-131-eBL7GtltKj@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 #5 from liaichun <liaichun at huawei dot com> ---
(In reply to Andreas Schwab from comment #4)
> no_more is set in both branches.

----do you mean here:
      no_more = nip == (service_user *) -1l;
      while (no_more == 0)
  when call again, nip is 0x0,  and no_more is also zero;

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-05-25 10:00 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 [this message]
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
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-eBL7GtltKj@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).