-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deserialization issues with 3.2.3-r8 #36
Comments
To follow up here, I see this on all non My test setup has:
And while the type is correct in struct Color : CommonAPI::Enumeration< uint32_t> {
enum Literal : uint32_t {
Red = 1111,
Green = 2222,
Blue = 3333,
Teal = 4444
}; It still fails the deserialization. I'm curious if it's because the typedef CommonAPI::SomeIP::EnumerationDeployment<uint8_t> ColorDeployment_t; I don't have a good grasp on the deployment types yet so this is taking a while to get to the bottom of. |
I haven't been able to narrow down the exact cause yet, but with 3.2.3-r8 I'm seeing seserialization issues. Not 100% of the time, but 100% reproducible. I'm trying to build a minimal example now that exposes the issue.
Has any one else seen this?
In this hard to read log where I filled the serialization/deserialization with debug:
You can see that the
65333
is written as5
This happens 100% at this call, but there are other calls where serialization/deserialization is fine.
One particular pattern that coordinates with this is when proxy calls are in callbacks (which emits a
BLOCKING CALL AVAILABLITY
vsomeip warning)i.e.
this is a bad pattern and I'm trying to get rid of it anyways, BUT:
In the mean time, I've had to modify 3.2.0 to be compatible with vsomeip 3.4.10 and the 3.1.14 generators (basically change
uid
/gid
forsec_client_t
)The text was updated successfully, but these errors were encountered: