Dr. Memory problems with Qt 5.5.0 gui applications?

[Tom Conijn]

Hello, I'm having trouble running Dr. Memory on Windows 10.

Dr. Memory is crashing with a internal error almost directly.
I have tried the latest stable release (1.9.1) and the latest build i could find (1.9.16845 build 178560794 built on Feb 13 2016 21:22:18)

This happens with debug versions of applications i create with Qt 5.5.0 that use the gui. (Just a default gui project)
It looks like Dr. Memory works correctly with release versions. It also seems to work with debug versions of non gui qt applications.

I tried some of the steps in "narrowing down the source of the problem", but it al results in the same error.

I attached 2 pictures of the cmd + crash window, when i run with the debug arguments.

Any help or information what can cause this problem would be appreciated.

Tom

[Derek Bruening]

Does your 32-bit application create 64-bit child processes?

--

---
You received this message because you are subscribed to the Google Groups "Dr. Memory Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drmemory-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Conijn]

No i don't think so, (But is there a good way to double check that?)

The default gui project for qt contains the following code:

#include "mainwindow.h"
#include <QApplication>

 int main(int argc, char *argv[])
 {
 QApplication a(argc, argv);
 MainWindow w;
 w.show();
 return a.exec();
 }

But even when i remove the mainwindow lines, it still has the same crash. 

Link to the debug executable from the above code: https://drive.google.com/file/d/0BxbZWaiWbbwRdVdlRi16eWdSMUU/view?usp=sharing
(It's a bit large size, because of the dynamic linking)

[Derek Bruening]

This is specific to Win10, right?  Xref https://github.com/DynamoRIO/dynamorio/issues/1898 where the same "cxt != NULL" assert was hit.  The assert (and release-build crash) are fixed in the latest Dr. Memory release -- however, there is more going on there that we did not have time to figure out, and a child process might not be followed into.  Also xref https://github.com/DynamoRIO/drmemory/issues/1859.

[Tom Conijn]

I tested it on Windows 10, but i'm not sure of it's a Windows 10 specific problem.
With the latest release (1.10.0) i get the following message:

drmemory.exe -debug -dr_debug -pause_at_assert testProject.exe

~~Dr.M~~ Dr. Memory version 1.10.0
~~Dr.M~~ Running "testProject.exe"
<legacy process creation detected: may miss child>
<Warning: NtGetContextThread called on unknown thread 0x00002294>
~~Dr.M~~ WARNING: application exited with abnormal code 0xff

I think this output is expected right?
I also see in the log file that unhandled system calls are found, But i have no idea if this is important..

I also have a Windows 7 pc where i tested some things.
I tested with version 1.9.16845 and the latest version 1.10.0

With version 1.9.16845 i got the following output:
drmemory.exe -debug -dr_debug -pause_at_assert testProject.exe

~~Dr.M~~ Dr. Memory version 1.9.16845
~~Dr.M~~ Running "testProject.exe"
~~Dr.M~~ WARNING: application exited with abnormal code 0xff

With the latest release i got the following output:
drmemory.exe -debug -dr_debug -pause_at_assert testProject.exe

~~Dr.M~~ Dr. Memory version 1.10.0
~~Dr.M~~ Running "testProject.exe"
~~Dr.M~~ WARNING: application exited with abnormal code 0xff

In the latest release i get no warning about the legacy process, but in the older version it also seems to exit without stopping at the assert.
So maybe this pc has some other problems and then it's beter not to look at this results.

In ~8 hours i will also test it on a windows 8 pc.

[Derek Bruening]

In https://github.com/DynamoRIO/drmemory/issues/1859 a small QLabel app runs fine on Win10.

I tried a QMainWindow-based app built w/ VS2015 and run on Win10 and I did in fact see an app crash, though it does not match yours: this is a seg fault.  Plus, it runs fine under plain DR, and I do not see the "legacy process creation".  I filed https://github.com/DynamoRIO/drmemory/issues/1867 for this app crash.