Wireshark-bugs: [Wireshark-bugs] [Bug 8279] Add support for Android Logcat logs, text files and
Comment # 19
on bug 8279
from Michal Labedzki
(In reply to comment #16)
> (In reply to comment #6)
> Aren't there already hex file viewers out there? Why must Wireshark expand
> to the point where it can handle *arbitrary* files? Shall we next add
> support for, say, Word documents, so that it can act as a Word document
> reader?
> > Also we can use Wireshark as text viewer
>
> We can also use vi and emacs as text viewers; why do we need Wireshark to be
> able to do it?
In future Wireshark will support everything, wont't it? Now supported are PNG,
JPG, XML... Hmm... Add Word dissector can be interested for Open/LibreOffice
teams and other developers :)
Hex view can be useful for:
1. Decode as... feature (see below example)
2. See why Wireshark does not open file which should - broken files. Don't you
ever try to open broken log/dump file?
(In reply to comment #17)
> (In reply to comment #5)
> > Created attachment 10000 [details]
> > [PATCH 1/2] Wiretap: Add support for text files
> >
> > This patch add support for text-files. Line is treat as packet. This can be
> > used for code review - case: reviewer put comment at one of line.
>
> Perhaps that functionality belongs in code review tools, not
> packet-capture-and-display tools.
>
> > Great with
> > pcap (need request to tcpdump, I hope that will be good to do that after
> > implementing it in Wireshark).
>
> I'm not convinced it's useful in Wireshark, so I'm not convinced it'd be
> useful in arbitrary capture programs.
What about text-based interfaces? For example Bluetooth HFP is next text
protocol over RFCOMM. I want to open this text file in Wireshark, than Decode
as HFP.
To be sure: "Android" patch does not require "text" patch, so can be applied
first. On the other side, Android very like text files contain "logcat" logs,
so why does not open it too? (it can be captured like DBus payload)
You are receiving this mail because:
- You are watching all bug changes.
