kinit locking up

[Russ Allbery]

Jon DeVree <jadevree at mtu.edu> writes:

>> Or, reversing for little-endian values, "/krb5.co".  That suggests  
>> some memory corruption, or initialization not happening.  Could you  
>> try valgrind or electric fence and see if they spot any problems?

> I'll try that, never used them before though.

Just apt-get install valgrind and then run:

    valgrind kinit

and it will spew out lots of memory debugging.  You can use the --log-file
option to specify a file to which the output should go instead.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>