| Bug ID |
11917
|
| Summary |
Custom types dissection in RTPS
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14171 [details]
regular communication
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
In a previous patch, I submitted a change to show the Topic Name and Type Name
for a given sample (storing it temporarily in Wireshark, since that information
is sent before in previous samples).
Now, we can use that information to try to dissect the serialized data. We can
call a dissector (if it exists) using the Type Name. This would let us see the
content deserialized, what is a big deal for most DDS users that use Wireshark
to debug their systems. Attaching a couple of captures, the plugin library I
built to dissect the custom type (Ubuntu 12 64 bits) and a couple of
screenshots showing how it works.
You are receiving this mail because:
- You are watching all bug changes.