Wireshark-bugs: [Wireshark-bugs] [Bug 12616] `tshark -T fields -e data` crashes in versions afte
Jeff Morriss
changed
bug 12616
What |
Removed |
Added |
Status |
UNCONFIRMED
|
CONFIRMED
|
CC |
|
jeff.morriss.ws@gmail.com
|
Hardware |
x86
|
All
|
Version |
unspecified
|
Git
|
Summary |
in >wireshark-2.0.2, tshark follow ssl stream segfaults
|
`tshark -T fields -e data` crashes in versions after 2.0.x
|
Ever confirmed |
|
1
|
Comment # 3
on bug 12616
from Jeff Morriss
I can reproduce in trunk. Backtrace is:
#0 0x00007ffff44949bc in get_node_field_value (fi=0x7fffe4e5b820, edt=0x0) at
../../epan/print.c:2288
#1 0x00007ffff4494a51 in proto_tree_get_node_field_values
(node=0x7fffe4e5b890, data="" at ../../epan/print.c:2027
#2 0x00007ffff4495ffc in proto_tree_children_foreach (tree=<optimized out>,
func=func@entry=0x7ffff4494a10 <proto_tree_get_node_field_values>,
data="" at ../../epan/proto.c:688
#3 0x00007ffff4492846 in write_specified_fields
(format=format@entry=FORMAT_CSV, fields=0xc75980, edt=edt@entry=0xcbecb0,
fh=0x7ffff1d83400 <_IO_2_1_stdout_>, cinfo=0x640140 <cfile+544>,
cinfo=0x640140 <cfile+544>) at ../../epan/print.c:2079
#4 0x00007ffff4493b3a in write_fields_proto_tree (fields=<optimized out>,
edt=edt@entry=0xcbecb0, cinfo=cinfo@entry=0x640140 <cfile+544>, fh=<optimized
out>) at ../../epan/print.c:426
#5 0x000000000041605d in print_packet (cf=cf@entry=0x63ff20 <cfile>,
edt=edt@entry=0xcbecb0) at ../tshark.c:3841
#6 0x000000000041670b in process_packet (cf=cf@entry=0x63ff20 <cfile>,
edt=edt@entry=0xcbecb0, offset=<optimized out>, whdr=0xc78b80,
pd=pd@entry=0xcc05d0 "", tap_flags=tap_flags@entry=0) at ../tshark.c:3429
#7 0x000000000040e6c3 in load_cap_file (cf=0x63ff20 <cfile>,
max_byte_count=<optimized out>, max_packet_count=<optimized out>,
out_file_name_res=<optimized out>, out_file_type=<optimized out>,
save_file=0x0)
at ../tshark.c:3171
#8 main (argc=<optimized out>, argv=<optimized out>) at ../tshark.c:1873
The problem is that 'edt' is NULL.
Minimal command line to reproduce appears to be:
% tshark -r <file> -T fields -e data
The file itself doesn't appear to matter (I can reproduce it with other files
too).
You are receiving this mail because:
- You are watching all bug changes.