On 3 May 2002, Dag-Erling Smorgrav wrote:

> [EMAIL PROTECTED] (Peter S. Housel) writes:
> > Current -CURRENT won't let me run "su"; it dies with SIGSEGV.  The
> > backtrace says:
> Yep, I see what the error is.  All I can say is "arrrgh!" since I've
> been running this code for a while now and it never segfaults on my
> box :(

DES: also seeing problems with ftpd:

it dumps core on signal 10

a gdb/backtrace of it:

#0  0x280cd9c7 in openpam_add_module () from /usr/lib/libpam.so.2
(gdb) bt
#0  0x280cd9c7 in openpam_add_module () from /usr/lib/libpam.so.2
#1  0x280ccc58 in openpam_dispatch () from /usr/lib/libpam.so.2
#2  0x280cce1a in openpam_dispatch () from /usr/lib/libpam.so.2
#3  0x280ccedf in openpam_configure () from /usr/lib/libpam.so.2
#4  0x280caf13 in pam_start () from /usr/lib/libpam.so.2
#5  0x804c50a in getsockname ()
#6  0x804c749 in getsockname ()
#7  0x8050c98 in getsockname ()
#8  0x804b71d in getsockname ()
#9  0x804ac05 in getsockname ()



Trish Lynch                                     [EMAIL PROTECTED]
FreeBSD                                         The Power to Serve
Ecartis Core Team                               [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to