zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Vin Shelton <acs@alumni.princeton.edu>
Cc: zsh-workers@zsh.org
Subject: Re: segfault in opensuse-11.2 latest CVS sources
Date: Thu, 10 Dec 2009 22:33:55 -0800	[thread overview]
Message-ID: <20091211063355.GA5006@redoubt.spodhuis.org> (raw)
In-Reply-To: <20a807210912101739k33fd835y737e24317da9c92@mail.gmail.com>

On 2009-12-10 at 20:39 -0500, Vin Shelton wrote:
> It looks like it's crashing in setpwent().  The code in hashtable.c
> seems pretty straightforward.  Have I misconfigured my system somehow?

Yes.  Or your vendor provided a buggy system.

Look at /etc/nsswitch.conf.

Are you using NIS or something, so that you need libnss_compat?  If not,
I'd change s/compat/files/g in the values in /etc/nsswitch.conf and
remove the _compat entries.  One less library probed in every binary
doing any kind of name resolution, one less thing to go wrong.

If you're getting an abort() call inside free() then free() has been
passed a bad memory location, so if this is happening inside setpwent()
then something's very wrong down there.  Perhaps you've removed
nsswitch.conf or you've removed some of its contents.  Perhaps there's a
major platform bug.

But this is almost certainly not a zsh issue.

> Anyway, here's the backtrace:
> 
> #0  0x00007fd7890b04e5 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00007fd7890b04e5 in raise () from /lib64/libc.so.6
> #1  0x00007fd7890b19b0 in abort () from /lib64/libc.so.6
> #2  0x00007fd7890eb66d in ?? () from /lib64/libc.so.6
> #3  0x00007fd7890f0c76 in ?? () from /lib64/libc.so.6
> #4  0x00007fd7890f596c in free () from /lib64/libc.so.6
> #5  0x00007fd788c6dc2a in ?? () from /lib64/libnsl.so.1
> #6  0x00007fd788c6dd5a in _nsl_default_nss () from /lib64/libnsl.so.1
> #7  0x00007fd788a58b61 in _nss_nis_setpwent () from
> /lib64/libnss_nis.so.2
> #8  0x00007fd788e78514 in ?? () from /lib64/libnss_compat.so.2
> #9  0x00007fd788e78686 in _nss_compat_setpwent () from
> /lib64/libnss_compat.so.2
> #10 0x00007fd789160850 in ?? () from /lib64/libc.so.6
> #11 0x00007fd78911d3fc in setpwent () from /lib64/libc.so.6

Regards,
-Phil


      reply	other threads:[~2009-12-11  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20a807210912101737r144e6da0r57d37b489cc00eb0@mail.gmail.com>
2009-12-11  1:39 ` Vin Shelton
2009-12-11  6:33   ` Phil Pennock [this message]

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=20091211063355.GA5006@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=acs@alumni.princeton.edu \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).