-On [20000221 14:40], Yoshinobu Inoue ([EMAIL PROTECTED]) wrote:
>> >Now I am very much interested in the value of
>> >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and
>> >possibly other flags are just set, or completely broken data
>> >is written on it.
>>
>> 893
>> (kgdb) print tp->tt_persist->c_flags
>> $1 = 0
>
>Woops sorry I was worng.
>tp->tt_rexmt->c_flags is actually causing the panic, and the
>necessary data is the contents of the tp->tt_rexmt->c_flags.
(kgdb) print tp->tt_rexmt->c_flags
$1 = 6
(kgdb) print tp->tt_rexmt
$2 = (struct callout *) 0xd5ce6c2c
(kgdb) print (*tp->tt_rexmt)
$3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c,
tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60,
c_func = 0xc018bcdc <tcp_timer_rexmt>, c_flags = 6}
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
<[EMAIL PROTECTED]> bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
