[Martin Visser <martinvisser99@xxxxxxxxx>]

Sake,

Not saying that this isn't a good idea (being able to output repeated fields), but I suspect when it gets to stable you might get some complaints. If people use "-T fields" like they do a CSV file, they might be expecting a fixed number of columns. (Currently whether there are 0, 1 or  more instances, I think there are always the same number of commas).

You might want to think about adding this new feature only by adding a new switch (say the -E aggregator switch)

Regards, Martin

MartinVisser99@xxxxxxxxx

On Thu, Jul 15, 2010 at 4:43 AM, Sake Blok <sake@xxxxxxxxxx> wrote:

Hi,

Recently a lot of questions have been asked on this list (and also at Sharkfest) about the output of 'tshark -T fields -e <field>' when <field> had multiple occurrences in one packet. Only the last occurrence was printed by tshark. I submitted a fix that now prints all occurrences, aggregated by commas (which can be overwritten with -E aggregator=<char>).

The fix will be included in version 1.6.x as well as in the next development release (1.5.x). For the impatient, please use an automated build from http://www.wireshark.org/download/automated/ (look for a version 33504 or higher).

Enjoy!
Cheers,


Sake

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe