Ah, I was thinking of bug 8511, which isn't quite the same (though close enough to twig my memory). This might make it easier to fix though? I've never dug into editcap in any detail.
Hmm, I couldn't find one. There were some editcap-related bugs open, but I didn't see one specifically for this feature or even where this feature would resolve the bug by luck. Maybe I'm missing it too though.I added this as a way to help simplify the steps I outlined in my answer to http://ask.wireshark.org/questions/24370/extracting-data-from-gtp-protocol (and forgot to mention that in the commit log), but also because I think it's generally useful. If it also resolves a bug though, then even better! But I don't think so.-----Original Message-----From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Evan HuusSent: Sunday, September 08, 2013 4:44 PMTo: wireshark-dev@xxxxxxxxxxxxxSubject: Re: [Wireshark-dev] [Wireshark-commits] rev 51845: /trunk/ /trunk/doc/: editcap.pod /trunk/docbook/: release-notes.asciidoc /trunk/: editcap.cIIRC there is (or was) a ticket open for this feature, if somebody remembers which one that would be nice, or I will try and learn bugzilla's search function again :)On 2013-09-08, at 8:29 PM, cmaynard@xxxxxxxxxxxxx wrote:http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=51845
User: cmaynard
Date: 2013/09/08 01:29 PM
Log:
Allow an optional offset to be specified when chopping bytes from packets.
Directory: /trunk/doc/
Changes Path Action
+14 -5 editcap.pod Modified
Directory: /trunk/docbook/
Changes Path Action
+3 -0 release-notes.asciidoc Modified
Directory: /trunk/
Changes Path Action
+82 -24 editcap.c Modified
CONFIDENTIALITY NOTICE: The information contained in this email message is intended only for use of the intended recipient. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately delete it from your system and notify the sender by replying to this email. Thank you.___________________________________________________________________________Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>Archives: http://www.wireshark.org/lists/wireshark-devUnsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|