Print

Print


* operational: we should not have tried Krb5 (this must be "automatic", to my knowledge we did not tell it to..). Will try to explicitly disable this. (these machine do not run EOS-specific code, btw).
* code: it should not crash..
```
#0  0x00007f36ee875ec4 in krb5_cc_get_principal (context=0x7f37381d9910, cache=0x0, principal=0x7f371b12f9e8) at ccfns.c:142
142	    return cache->ops->get_princ(context, cache, principal);
(gdb) l krb5_cc_get_principal
138	krb5_error_code KRB5_CALLCONV
139	krb5_cc_get_principal(krb5_context context, krb5_ccache cache,
140	                      krb5_principal *principal)
141	{
142	    return cache->ops->get_princ(context, cache, principal);
143	}
$1 = (struct _krb5_ccache *) 0x0
(gdb) up
#1  0x00007f36ef52dfe7 in XrdSecProtocolkrb5::get_krbCreds (KP=<optimized out>, krb_creds=krb_creds@entry=0x7f3734205930)
    at /usr/src/debug/xrootd/xrootd/src/XrdSeckrb5/XrdSecProtocolkrb5.cc:695
695	   if ((rc = krb5_cc_get_principal(krb_client_context, krb_client_ccache, &mycreds.client)))
(gdb) print krb_client_ccache
$2 = (krb5_ccache) 0x7f37381d91f0
```
So this function is sufficiently simple that it should not "forget" the CCache between two lines, which implies some concurrency thing..

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/395#issuecomment-232652498

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1