So do you have an idea where the problem lies? A bug in my code? An
error in my design? An incorrect call to wireshark functions?
Here's some output from my program, printing info from pinfo before call
to tcp_dissect_pdus, in each "get length" call, and in each each dissector:
//before call to tcp_dissect_pdu
++++++++++++++++++++++++++++++++++++++++++++++
pinfo:
fragmented:1
can_desegment:0
saved_can_desegment:0
desegment_offset:0
desegment_len:0
want_pdu_tracking:0
bytes_until_next_pdu:0
pinfo->fd
pkt_len:1514
cap_len:1514
cum_bytes:1514
//first pdu
get message len:1088
dissect message len:1088
pinfo: //called in dissector
fragmented:1
can_desegment:0
saved_can_desegment:0
desegment_offset:0
desegment_len:0
want_pdu_tracking:0
bytes_until_next_pdu:0
pinfo->fd
pkt_len:1514
cap_len:1514
cum_bytes:1514
//second pdu
get message len:144
dissect message len:144
pinfo: //called in dissector
fragmented:1
can_desegment:0
saved_can_desegment:0
desegment_offset:0
desegment_len:0
want_pdu_tracking:0
bytes_until_next_pdu:0
pinfo->fd
pkt_len:1514
cap_len:1514
cum_bytes:1514
//third pdu
get message len:1900
dissect message len:1900
pinfo: //called in dissector
fragmented:1
can_desegment:0
saved_can_desegment:0
desegment_offset:0
desegment_len:0
want_pdu_tracking:2
bytes_until_next_pdu:1684
pinfo->fd
pkt_len:1514
cap_len:1514
cum_bytes:1514
//whoops, exception throw. tcp_dissect_pdus doesn't return nornmally
Thanks,
Andy
>>_______________________________________________
>>Wireshark-dev mailing list
>>[email protected]
>>http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
_______________________________________________
Wireshark-dev mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-dev
