Russ Allbery <[EMAIL PROTECTED]> writes:
> I'm checking to see if I can duplicate the problem now.
Here's the backtrace:
Core was generated by `./krb5context'.
Program terminated with signal 11, Segmentation fault.
#0 gss_krb5_init_sec_context (minor_status=0x7fff0f1c180c,
initiator_cred_handle=<value optimized out>,
context_handle=0x7fff0f1c17e8, target_name=0x5051d0,
mech_type=<value optimized out>, req_flags=14, time_req=0,
input_chan_bindings=0x0, input_token=0x7fff0f1c17c0, actual_mech_type=0x0,
output_token=0x7fff0f1c17b0, ret_flags=0x0, time_rec=0x0) at context.c:147
147 rc = shishi_ap_rep_der_set (k5->ap, data + TOK_LEN, datalen -
TOK_LEN);
(gdb) bt
#0 gss_krb5_init_sec_context (minor_status=0x7fff0f1c180c,
initiator_cred_handle=<value optimized out>,
context_handle=0x7fff0f1c17e8, target_name=0x5051d0,
mech_type=<value optimized out>, req_flags=14, time_req=0,
input_chan_bindings=0x0, input_token=0x7fff0f1c17c0, actual_mech_type=0x0,
output_token=0x7fff0f1c17b0, ret_flags=0x0, time_rec=0x0) at context.c:147
#1 0x0000000000401451 in main (argc=<value optimized out>,
argv=<value optimized out>) at krb5context.c:294
The same test passes when built with -g and no optimization flags. k5
isn't NULL or anything obvious, so I'm not sure where the segfault is
coming from.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
_______________________________________________
Help-gss mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gss
