Wireshark mailing list archives
wireshark crash with segmentation fault
From: Hardik Patel <hardik.party () gmail com>
Date: Fri, 2 Aug 2013 14:54:10 +0200
Hi, I come accross a problem in which some time wireshark crash and i can see "segmentation fault" on console. i have created dissector in which i guess problem with tree struct and ett variables, i think i have not properly define. I read that *The expansion of this node is controlled by the ett_foovariable. * for example i click on packet frame which have long tree and than i move directly to packet frame which has smaller tree. so i guess wireshark remember that last time i have open 5th element of tree but this time packet frame do not have 5 element so it crash. below is those two packet frame in snapshot. [image: Inline image 2] and second has packet frame has only three elements on tree: [image: Inline image 3] so i dont want wireshark to remember what i have opened last. Thank you very much. Hardik Patel Regards, Hardik Patel
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- wireshark crash with segmentation fault Hardik Patel (Aug 02)
- Re: wireshark crash with segmentation fault Jeff Morriss (Aug 02)
- Re: wireshark crash with segmentation fault Hardik Patel (Aug 05)
- Message not available
- Re: wireshark crash with segmentation fault Hardik Patel (Aug 05)
- Re: wireshark crash with segmentation fault Jeff Morriss (Aug 05)
- Re: wireshark crash with segmentation fault Hardik Patel (Aug 05)
- Re: wireshark crash with segmentation fault Jeff Morriss (Aug 02)