kinit locking up

[Ken Raeburn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Dec 10, 2005, at 19:58, Jon DeVree wrote:
> On Sat, Dec 10, 2005 at 03:32:27PM -0800, Russ Allbery wrote:
>> If you run kinit under strace, what is it doing after you enter your
>> password?  Nothing at all?
>
> connect(4, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("10.0.3.1")}, 28) = 0
> fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
> fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK)  = 0
> gettimeofday({1134262677, 201560}, NULL) = 0
> poll([{fd=4, events=POLLOUT, revents=POLLOUT}], 1, 0) = 1
> send(4, "\307\300\1\0\0\1\0\0\0\0\0\0\5tesla\5setec\0\0\1\0\1", 29,  
> 0) =
> 29
> poll([{fd=4, events=POLLIN, revents=POLLIN}], 1, 5000) = 1
> ioctl(4, FIONREAD, [59])                = 0
> recvfrom(4, "\307\300\205\200\0\1\0\1\0\1\0\0\5tesla\5setec\0\0\1 
> \0"...,
> 1024, 0, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("10.0.3.1")}, [16]) = 59
> close(4)                                = 0
> gettimeofday({1134262677, 204715}, NULL) = 0
> time(NULL)                              = 1134262677
> futex(0x804d2f4, FUTEX_WAIT, 2, NULL)   = -1 EINTR (Interrupted system
> call)

I'm not sure what mutex would be getting locked at that point.  If  
you're rebuilding binaries, could you try building with -g and get a  
stack trace in gdb when this happens?  If it's in one of the libkrb5  
mutex-handling macros, the mutex object we use should include a file  
name and line number where the mutex was last locked or unlocked;  
that would be useful to know too.

Ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDndYqUqOaDMQ+e5gRAtCrAJ9oqYU7T/HGDSqJNIRWruUVc+hbnACgyDJr
DrUuDDuP08XhTbbYnGsFMzY=
=Q3Yo
-----END PGP SIGNATURE-----