Peter Maydell <peter.maydell@xxxxxxxxxx> wrote:
> On Mon, 15 Jul 2019 at 14:44, Juan Quintela <quintela@xxxxxxxxxx> wrote:
>>
>> Peter Maydell <peter.maydell@xxxxxxxxxx> wrote:
>> > On Fri, 12 Jul 2019 at 17:33, Peter Maydell <peter.maydell@xxxxxxxxxx> wrote:
>> >> Still fails on aarch32 host, I'm afraid:
>>
>> Hi
>>
>> dropping the multifd test patch from now. For "some" reason, having a
>> packed struct and 32bits is getting ugly, not sure yet _why_.
>
> IMHO 'packed' structs are usually a bad idea. They have a bunch
> of behaviours you may not be expecting (for instance they're
> also not naturally aligned, and arrays of them won't be the
> size you expect).
I can't get everything happy O:-)
For the multifd initial packet, I used to have that I wrote the fields
by hand. Then danp asked that I used a packed struct, and converted the
values inside it. So ..... Imposible to have everybody happy.
Anyways, the struct is packed, both sides are i386 32bits, and it should
be exactly the same, but it appears that there is where your valgrind
problems appear. Still investigating _where_ the problem is. What is
even weirder is that there is no error at all on 64bits.
Thanks, Juan.
PS. BTW, did you launched by hand the guests with valgrind, or there is
a trick that I am missing for launching a qtest with valgrind?
