On Fri, Aug 03, 2012 at 06:23:13PM +0000, Christopher Maynard wrote: > Martin Mathieson <martin.r.mathieson@...> writes: > > > Interesting. How could I find the bug that a given attached file was > associated with? e.g. this one: > > > > > > http://bugs.wireshark.org/bugzilla/attachment.cgi?id=4678: dct2000 mac-lte > rlc-lte > > Unknown.
Try Google ;-) site:wireshark.org/lists/wireshark-bugs "Created an attachment (id=4678)" Shows sample crash for bug #4413 (http://www.wireshark.org/lists/wireshark-bugs/201005/msg00461.html) > I'm not entirely sure how Jakub generated the list. for ((i=1; i < 8860; i++)); do wget https://bugs.wireshark.org/bugzilla/attachment.cgi?id=$i; done Later I moved all capture files (if they can be loaded with wiretap) to seperated directory and ran list_protos_in_cap.sh * Generally it's not best, some capture files are compressed with 7z/ zip, some are in tarballs. But I hope most of capture files are on the list. Cheers, Kuba. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
