--On Tuesday, July 24, 2001 01:21:43 -0400 Derrick J Brashear
<[EMAIL PROTECTED]> wrote:
> Does truss show anything useful happening? If not, try sotruss, and see if
> that tells you anything.
This seems to be the relevant part from truss:
3932: fork() = 3938
3938: fork() (returning as child ...) = 3932
3938: Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7E1019A0
3938: siginfo: SIGSEGV SEGV_MAPERR addr=0x0025DDA0
3938: Received signal #11, SIGSEGV [default]
3938: siginfo: SIGSEGV SEGV_MAPERR addr=0x0025DDA0
3938: *** process killed ***
3932: waitid(P_PID, 3938, 0xFFFFFFFF7FFFB940, WEXITED|WTRAPPED) = 0
3932: sigaction(SIGCLD, 0xFFFFFFFF7FFFBA20, 0x00000000) = 0
3932: sigaction(SIGCLD, 0xFFFFFFFF7FFFBA20, 0xFFFFFFFF7FFFBB10) = 0
3932: fork() = 3940
3940: fork() (returning as child ...) = 3932
3940: Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7E1019A0
3940: siginfo: SIGSEGV SEGV_MAPERR addr=0x0025DDA0
3940: Received signal #11, SIGSEGV [default]
3940: siginfo: SIGSEGV SEGV_MAPERR addr=0x0025DDA0
3940: *** process killed ***
Does that mean anything to anyone? Again, that's the 1.1.1 PAM module
running against a 1.0.4 installation...
What's interesting is that the SASL library apparently does not use libpam,
but instead it parses pam.conf itself and it accesses the modules
directly... Not sure if that's relevant, though.
Cheers, Sebastian Hagedorn
--
Sebastian Hagedorn M.A. - RZKR, Zimmer 18
Zentrum f�r angewandte Informatik - Unversit�tsweiter Service RRZK
Universit�t zu K�ln / Cologne University - Tel. +49-221-478-5587
PGP signature
