You could use a bisection method. Split the file in 2 smaller and try both. Continue until you have 1 packet. Once you have the guilty, you can give it to the different softwares (wireshark, tshark, reordercap, mergecap, etc). If only one crashes, the bug is located there. If all crash probably the bug is in some lib (libwireshark?). Hope it helps. Dario
On Mon, Aug 26, 2013 at 11:31 AM, Danniel_zeng <cheer_z...@163.com> wrote: > Hi all, > > The wireshark(we have added some something) crashes while I export the > packet(regardless which packet). > And this only happens with the captures in our lab . > It is hard to discover which message cause this issue,as there is not > output in the console window at all. > > So I would like to know which method can I use to locate the bug. > > Thanks! > > > > ___________________________________________________________________________ > 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-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe
