[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#165358: Also caused segfaults in su and ssh

On Wed, Oct 23, 2002 at 11:55:04AM -0700, Jeff Bailey wrote:
> On Wed, Oct 23, 2002 at 01:45:37PM -0500, Zed Pobre wrote:
> >     This is a major problem -- this means that producers of
> > binary-only software have no way of reliably producing a working
> > binary under an arbitrary Debian release (or, for that matter, under
> > any glibc-based distribution), and while I am somewhat sympathetic
> > to a viewpoint of not greatly supporting non-free software", I'm
> > also in a position of having to use and support a fair amount of it
> > because there is no free equivalent.  Is there any way to get the
> > NSS code also statically linked?  I have a memory of this not being
> > a problem at one point in the past.
> Let's first take a look at what the problem is.  If you can reproduce
> with zsh-static, then we have a hope of getting an answer for why -3
> doesn't solve it in that case.

    Oh, I can trivially reproduce.  On any machine.  I'll probably
need to recompile zsh with debugging enabled to get useful results,
but here's an initial backtrace for you:

singularity:~> gdb zsh-static
GNU gdb 2002-08-18-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /bin/zsh-static 
warning: shared library handler failed to enable breakpoint

Program received signal SIGSEGV, Segmentation fault.
0x08122ed3 in ?? ()
(gdb) backtrace
#0  0x08122ed3 in ?? ()
#1  0x0811cbeb in ?? ()
#2  0x0810b04e in ?? ()
#3  0x0811ce52 in ?? ()
#4  0x0810b9a8 in ?? ()
#5  0x0810b04e in ?? ()
#6  0x0810b963 in ?? ()
#7  0x0810ba18 in ?? ()
#8  0x08104775 in ?? ()
#9  0x08104470 in ?? ()
#10 0x081053dd in ?? ()
#11 0x081012bf in ?? ()
#12 0x08100eff in ?? ()
#13 0x08065f67 in ?? ()
#14 0x08067395 in ?? ()
#15 0x080481c8 in ?? ()
#16 0x080dee25 in ?? ()

This is with libc6 2.3.1-3 and zsh-static 4.0.6-13.  Let me know if
you want me to recompile libc6, zsh-static, or both, or if there's
anything more I can do to be helpful.

> As far as long term support and static NSS, I would probably have to
> refer you directly to upstream.  I don't have a good answer, but I
> suspect it's just one of those platform quirks. =(

    If it can't be fixed, then I actually go back to my recommendation
that we stop shipping libc.a, and recommend to upstream that they drop
support for libc.a, because it's basically a sham.

Zed Pobre <zed@debian.org> a.k.a. Zed Pobre <zed@resonant.org>
PGP key and fingerprint available on finger; encrypted mail welcomed.

Attachment: pgpZi9o2ULnm2.pgp
Description: PGP signature

Reply to: