feat: Add additional logging tags for protocol information #593
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This MR adds the following; currently DRAFT for experiments:
io={TYPE}
;TYPE
is eitherread
orwrite
proto={PROTO}
;PROTO
is one of the supported protocols in gallia, e.g.uds
ordoip
.encoding={ENCODING}
; optional;ENCODING
could behex
orbase64
hr
commands to interpret the tagged messagesThe motivation of this is, we have currently a "works somehow" dissector in
cursed_hr
for UDS. This dissector uses a best effort heuristic to detect UDS messages. However, this is not useful for messages of other types.gallia recently gained FlexRay support and a standardized dissection API in our
hr
commands would help everybody. For instance, for FlexRay there is already an own tool to help debugging.So, this MR is an attempt to standardize dissection in our toolchain by adding metadata to our logfiles and an extendable API for
hr
.Open Questions: