On Thu, 29 Jul 2021 14:37:28 +0200
"Damian Wrobel" <[email protected]> wrote:
> the PSEUDO_MSG_OP is being unconditionally assigned to the msg.type
> before any real usage of the 'msg' structure. So, if I'm not mistaken
> that code was already tested and didn't work well and was reverted
> here[1].
I don't think that's identical.
msg = (pseudo_msg_t) { .type = PSEUDO_MSG_OP };
zeros out a number of other fields.
Anyway, if it fails with msg declared static, I'd be interested in
a minimal reproducer for it, I don't see anything obvious that ought to
care about it, but I would easily believe that the other fields not
being zeroed out would cause weirdness, which is why I suggested a
complete assignment to it, not just overwriting the .type field.
-s
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#154250):
https://lists.openembedded.org/g/openembedded-core/message/154250
Mute This Topic: https://lists.openembedded.org/mt/84526799/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
