Michal Labedzki
changed
bug 8818
| What |
Removed |
Added |
| Attachment #11010 is obsolete |
|
1
|
| Attachment #11010 Flags |
review_for_checkin?
|
|
| Attachment #11019 Flags |
|
review_for_checkin?
|
Comment # 4
on bug 8818
from Michal Labedzki
Created attachment 11019 [details]
[PATCH] Add support for ELF files
(In reply to comment #2)
> Another candidate for FileShark?
No/Yes. I want to enroll to the group of developers that would like to do
dissections like this in Wireshark. However FileShark idea is ok, but probably
is not necessary/needed (Wireshark have everything in place)
(In reply to comment #3)
> Even if some folks disagree about Wireshark being the "right place" for it,
> this is pretty cool in terms of presentation (better than objdump). Might
> sort-of make sense for dissecting (malicious?) ELF payloads in (T)FTP/HTTP
> streams, or things like firmware update sessions, FWIW.
>
> The only snag that I can find is that the over-zealous error checking in the
> build scripts causes the process to trip up with:
>
> CC libdissectors_la-packet-elf-file.lo
> packet-elf-file.c: In function 'dissect_elf':
> packet-elf-file.c:993:22: error: 'dynstr_offset' may be used uninitialized
> in this function [-Werror=maybe-uninitialized]
> packet-elf-file.c:992:22: error: 'strtab_offset' may be used uninitialized
> in this function [-Werror=maybe-uninitialized]
> cc1: all warnings being treated as errors
> make[5]: *** [libdissectors_la-packet-elf-file.lo] エラー 1
>
> Was easy to work around by initialising those variables to 0, though.
Ok, fixed now. Thanks. Hmmm.. "./configure --enable-extra-gcc-checks" not
working for me?
> Seems to load a 32-bit x86 Linux executable ("/bin/ls"), a random 32-bit
> MIPS PlayStation 2 executable, and a random 64-bit PowerPC executable fine.
Great. Do you now where I can find free executables for other platforms then
x86-32/x86-64/arm? (for example your Playstation or PowerPC.. or.. something
else). I will be happy to see and testing this dissector on them.
You are receiving this mail because:
- You are watching all bug changes.
