Comment # 12
on bug 9247
from Jakub Zawadzki
(In reply to comment #11)
> START defrag: 0
> offset: 0 dfpos: 0 len: 1350
> [0x1333c00] -- 2 tvb_get_ptr(..., 0, 1350) 1350 1350
> ... tvb_get_ptr() OK2
> offset: 1350 dfpos: 1350 len: 1448
> [0x1333ad0] -- 2 tvb_get_ptr(..., 0, 207) 1448 1448
> ... tvb_get_ptr() OK2
> END
> ? [0x1333ad0] fd_i->len: 1350 tvb-len: 1557 1557 .... 1557 offset: 0
> ? [0x1333c00] fd_i->len: 1448 tvb-len: 207 207 .... 1557 offset: 1350
> ? [0x1333a80] fd_i->len: 109 tvb-len: 109 109 .... 1557 offset: 1448
> [0x13338a0] fd->len: 1339 tvb-len: 1339 1339
> [0x1333b20] fd->len: 1288 tvb-len: 1288 1288
> START defrag: 0
> offset: 0 dfpos: 0 len: 1350
> [0x1333ad0] -- 2 tvb_get_ptr(..., 0, 1350) 1557 1557
> ... tvb_get_ptr() OK2
> offset: 1350 dfpos: 1350 len: 1448
> [0x1333c00] -- 2 tvb_get_ptr(..., 0, 1448) 207 207
> [0x1178d40] fd->len: 1448 tvb-len: 1448 1448
> START defrag: 0
> offset: 0 dfpos: 0 len: 1350
Is it full log?
If full is big, can you at least attach | grep -- "->len"
I'm really interested if after creating TVB fd->len not equals tvb-len.
> ? [0x1333c00] fd_i->len: 1448 tvb-len: 207 207 .... 1557 offset: 1350
this one is causing exception, but it's just subset.
Sorry for lot of requests, but remote + only-printf-debugging is hard for me
also.
Thanks.
You are receiving this mail because:
- You are watching all bug changes.