https://bugs.winehq.org/show_bug.cgi?id=50842
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #1 from Bernhard Übelacker bernhardu@mailbox.org --- Created attachment 71355 --> https://bugs.winehq.org/attachment.cgi?id=71355 rr-debugging of testbot executable with wine
Hello François, I tried to reproduce this with an patch with just a few extra traces, but that did not show the crash. https://testbot.winehq.org/JobDetails.pl?Key=104228
So I downloaded the winetest64-latest.exe from the last batch test run, extracted msado15_test.exe and with this the crash is reproducible on testbot. Unfortunately those executables have the debug information stripped.
But still I wondered if the crashing address shown might be inside the test executable image itself. Therefore I tried to debug it inside wine setting the breakpoint to 0x408817 and it stopped: => 0x408817: mov (%rcx),%rax
And running backwards it seems this value in $rcx got created in wine by CoCreateInstance at msado15.c:596 and is finally the value of the variable recordset.
So one theory might be that the variable recordset gets overwritten later.
But is there a way to submit jobs to testbot, so they will run through winetest64-latest.exe, like in the batch runs?