diff options
| author | Gerald Combs <gerald@zing.org> | 2015-06-01 19:48:23 -0700 |
|---|---|---|
| committer | Gerald Combs <gerald@wireshark.org> | 2015-11-10 21:02:51 +0000 |
| commit | e9d1d003eaea57f2a94fd24b920a7c462b7ff4e0 (patch) | |
| tree | 17e61b76845adf6010210cb9bae33bb5207f23f7 /help | |
| parent | 0b5f6018afed4c58b86b0337934439a522025220 (diff) | |
| download | wireshark-e9d1d003eaea57f2a94fd24b920a7c462b7ff4e0.tar.gz wireshark-e9d1d003eaea57f2a94fd24b920a7c462b7ff4e0.tar.bz2 wireshark-e9d1d003eaea57f2a94fd24b920a7c462b7ff4e0.zip | |
Initial Sysdig syscall (event) support.
Add a dissector for reading Sysdig event blocks. It only handles plain
events but it's usable for reading trace files on hand here.
Use a script to generate various parts of the dissector. As an experiment,
update parts in-place instead of using a template.
Ultimately there should probably be a top-level "Syscall" or "Event"
dissector alongside the "Frame" dissector, which could then call this.
You could then directly compare an executable's system calls alongside
its network traffic.
For now leverage the pcapng_block dissector and keep everything under
"Frame".
Next steps:
- Items listed at the top of packet-sysdig-event.c.
Change-Id: I17077e8d7f40d10a946d61189ebc077d81c4da37
Reviewed-on: https://code.wireshark.org/review/11103
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
(cherry picked from commit 0d497e812508b3d71716618e39647a107c206b1d)
Reviewed-on: https://code.wireshark.org/review/11702
Diffstat (limited to 'help')
0 files changed, 0 insertions, 0 deletions