public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmueller at suse dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nscd/2114] nscd crashes all the time
Date: Sun, 08 Jan 2006 17:52:00 -0000	[thread overview]
Message-ID: <20060108175232.21937.qmail@sourceware.org> (raw)
In-Reply-To: <20060106172116.2114.dmueller@suse.com>


------- Additional Comments From dmueller at suse dot com  2006-01-08 17:52 -------
no, it also happens if somebody requests stuff that can't be cached by nscd,  
like for example RR DNS and similiar. Thats not necessarily a configuration  
problem.   
  
I agree that the assert() should be more restrictive as it is, but it looks 
inconsistent and quite confusing. either the 2nd one should be changed like in 
the patch, or an additional assert (db->data > db->head) should be added. Or 
the 3rd one could most likely be changed to refer to db->data as well instead 
of db->head like it does now. Would make the expression even simpler as well. 
 
Whatever you prefer, right now the asserts are pretty inconsistent though.  
 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW


http://sourceware.org/bugzilla/show_bug.cgi?id=2114

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-01-08 17:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 17:21 [Bug nscd/2114] New: " dmueller at suse dot com
2006-01-06 17:23 ` [Bug nscd/2114] " dmueller at suse dot com
2006-01-06 19:15 ` drepper at redhat dot com
2006-01-08 17:52 ` dmueller at suse dot com [this message]
2006-01-10  0:25 ` drepper at redhat dot com
2006-02-23 23:38 ` christophe at saout dot de
2006-03-05 10:34 ` christophe at saout dot de

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=20060108175232.21937.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).