I have already seen a SIG 11 posting in strchr which seems
to be the same cause ...
Program received signal SIGSEGV, Segmentation fault.
0x402c072f in strlen ()
(gdb) bt
#0 0x402c072f in strlen ()
#1 0x80cd058 in dissect_transact_params (pd=0x81dd380 "", offset=114,
fd=0x81fbe38, parent=0x0, tree=0x0, si={tid = 2048, uid = 2048,
mid = 9857, pid = 0, conversation = 0x82c4da8, request_val = 0x82d3d18},
max_data=408, SMB_offset=58, errcode=0, dirn=0, DataOffset=64,
DataCount=344, ParameterOffset=56, ParameterCount=8, TransactName=0x0)
at packet-smb.c:9023
#2 0x80ce141 in dissect_transact_smb (pd=0x81dd380 "", offset=114,
fd=0x81fbe38, parent=0x0, tree=0x0, si={tid = 2048, uid = 2048,
mid = 9857, pid = 0, conversation = 0x82c4da8, request_val = 0x82d3d18},
max_data=408, SMB_offset=58, errcode=0, dirn=0) at packet-smb.c:9647
#3 0x80d0e28 in dissect_smb (pd=0x81dd380 "", offset=90, fd=0x81fbe38,
tree=0x0, max_data=408) at packet-smb.c:11174
#4 0x80a2f6c in dissect_nbss_packet (pd=0x81dd380 "", offset=58,
fd=0x81fbe38, tree=0x0, max_data=412) at packet-nbns.c:1537
#5 0x80a3159 in dissect_nbss (pd=0x81dd380 "", offset=54, fd=0x81fbe38,
tree=0x0) at packet-nbns.c:1599
#6 0x80d416f in dissect_tcp (pd=0x81dd380 "", offset=54, fd=0x81fbe38,
tree=0x0) at packet-tcp.c:519
#7 0x80969e5 in dissect_ip (pd=0x81dd380 "", offset=34, fd=0x81fbe38,
tree=0x0) at packet-ip.c:920
#8 0x80671f5 in ethertype (etype=2048, offset=14, pd=0x81dd380 "",
fd=0x81fbe38, tree=0x0, fh_tree=0x0, item_id=225) at ethertype.c:82
#9 0x808b5c4 in dissect_eth (pd=0x81dd380 "", offset=14, fd=0x81fbe38,
tree=0x0) at packet-eth.c:202
#10 0x806de53 in dissect_packet (pd=0x81dd380 "", fd=0x81fbe38, tree=0x0)
at packet.c:815
[...]
Linux 2.2.13, glibc 2.0, Ethereal release 0.7.8
Flo
--
Florian Lohoff flo@xxxxxxxxxx +49-5241-470566
... The failure can be random; however, when it does occur, it is
catastrophic and is repeatable ... Cisco Field Notice
