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

Bug#165358: Also caused segfaults in su and ssh



On Fri, Oct 18, 2002 at 12:09:14PM -0700, Jeff Bailey wrote:
> On Fri, Oct 18, 2002 at 01:37:51PM -0500, Zed Pobre wrote:
> 
> > Attempting to su to root (even from root) with 2.3.1-1 on one of my
> > test systems caused an immediate segfault.  Also, attempting to ssh
> > to root on the same system allowed login, but then immediately died.
> > The problem was fixed by reverting libc6 and related package.  No
> > core files were left, but if it's important, I can probably be
> > persuaded to put the broken libc6 version back on and run su inside
> > of gdb.
> 
> The ssh problem is probably the known bug that anything using NSS
> needs to be restarted after the libc upgrade.  The next package will
> warn about that.
> 
> I've been using test versions of the 2.3 package for almost a month
> now and haven't seen any su segfaults.  Please investigate that
> further.

    I'm admittedly not that experienced at this sort of thing, but
this is bizarre:

shannon:~# gdb su
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/su 
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGTRAP, Trace/breakpoint trap.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x080480e0 in ?? ()
(gdb) backtrace
#0  0x080480e0 in ?? ()
Cannot access memory at address 0x0
(gdb) 


This make any sense to you?  Should I play around with recompiling su?

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

Attachment: pgpOeS31UBKRA.pgp
Description: PGP signature


Reply to: