[Bug 50842] The 64-bit msado15:msado15 test crashes

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50842

--- Comment #7 from Bernhard Übelacker <bernhardu at mailbox.org> ---
@Robert:
thanks for the tip with the test logfile - I have successfuly
overlooked this header.
I just found by strings in the executable an "GCC: (GNU) 8.3-win32 20190406",
but that alone made it not certain it is a Debian.

I fear the drmemory log could potentially reveal information about the
native implementation. Therefore will I not look into it until told otherwise.
I guess this is also the reason, why e.g. no backtrace is shown
in crashing test runs at windows. Maybe you want to mark this file
as outdated or someone removes it, if I am right.


Inside a Buster VM I could rebuild the crashing winetest executable:
https://testbot.winehq.org/JobDetails.pl?Key=104290

And added a few trace lines here,
which confirms my theory that variable recordset gets overwritten:
https://testbot.winehq.org/JobDetails.pl?Key=104291

Somewhere in this function call:
647        hr = Field_get_DefinedSize( field, &size );

And these test runs show that the variables size is just before
recordset in memory:
https://testbot.winehq.org/JobDetails.pl?Key=104299
https://testbot.winehq.org/JobDetails.pl?Key=104300

Following should show if native writes more than 4 bytes:
https://testbot.winehq.org/JobDetails.pl?Key=104301
(But unfortunately currently delayed by the batch runs ...)

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.