Re: exits right away

581 views
Skip to first unread message

tjw...@gmail.com

unread,
Jan 11, 2013, 12:01:01 PM1/11/13
to drmemor...@googlegroups.com

C:\Program Files\Dr. Memory\bin>drmemory.exe -version
Dr. Memory version 1.4.6 -- build 2

Qin Zhao

unread,
Jan 11, 2013, 2:07:51 PM1/11/13
to drmemor...@googlegroups.com
are you using a  non-ascii username, which might cause Dr.Memory fail to attach?

On Friday, January 11, 2013 11:57:37 AM UTC-5, tjw...@gmail.com wrote:
I'm trying to run the hello world example, but it exits right away and doesn't start notepad.  I'm running Windows 7 32-bit and my command prompt as an administrator.  Any ideas why this happens?  It also fails with the latest release

C:\Program Files\Dr. Memory\bin>drmemory.exe -logdir "." -v C:\Windows\notepad.e
xe
INFO: targeting application: "C:\Windows\notepad.exe"
INFO: app cmdline: "C:\Windows\notepad.exe"
INFO: logdir is "C:\Program Files\Dr. Memory\bin"
INFO: configuring notepad.exe pid=6860 dr_ops="-disable_traces -bb_single_restor
e_prefix -max_bb_instrs 256 "
INFO: configuring client "C:\Program Files\Dr. Memory/bin/release/drmemorylib.dl
l" ops="-logdir `C:\Program Files\Dr. Memory\bin` -resfile 6860 "
INFO: waiting for app to exit...
WARNING: unable to locate results file since can't open C:\Program Files\Dr. Mem
ory\bin/resfile.6860: 2





Derek Bruening

unread,
Jan 11, 2013, 2:11:40 PM1/11/13
to drmemor...@googlegroups.com
On Fri, Jan 11, 2013 at 2:07 PM, Qin Zhao <zha...@google.com> wrote:
are you using a  non-ascii username, which might cause Dr.Memory fail to attach?

Can you try the most recent build from http://build.chromium.org/p/client.drmemory/builds/ (these are slightly different format from official releases: self-extracting exes) which should have the non-ascii issue fixed, and other bug fixes, so we can rule out any known issues that have been fixed?

- Derek

tjw...@gmail.com

unread,
Jan 11, 2013, 2:35:06 PM1/11/13
to drmemor...@googlegroups.com
same thing.  my username is a string of ascii numbers.

D:\tools\drmemory\bin>drmemory.exe -logdir "." -v C:\Windows\notepad.exe
INFO: targeting application: "C:\Windows\notepad.exe"
INFO: app cmdline: "C:\Windows\notepad.exe"
INFO: logdir is "D:\tools\drmemory\bin"
INFO: using symbol path D:/tools/drmemory/bin/symbols as the local store
INFO: using symbol path srv*D:/tools/drmemory/bin/symbols*http://msdl.microsoft.
com/download/symbols to fetch symbols
INFO: configuring notepad.exe pid=9980 dr_ops="-disable_traces -bb_single_restor
e_prefix -max_bb_instrs 256 -no_early_inject -logdir `D:\tools\drmemory\bin/dyna
morio` "
INFO: configuring client "D:\tools\drmemory/bin/release/drmemorylib.dll" ops="-l
ogdir `D:\tools\drmemory\bin` -resfile 9980 "
INFO: waiting for app to exit...
WARNING: unable to locate results file since can't open D:\tools\drmemory\bin/re
sfile.9980: 2

D:\tools\drmemory\bin>drmemory.exe -version
Dr. Memory version 1.5.1160 -- build 42

D:\tools\drmemory\bin>

Qin Zhao

unread,
Jan 11, 2013, 2:50:55 PM1/11/13
to drmemor...@googlegroups.com
can you download dynamorio from http://code.google.com/p/dynamorio/downloads/list, and see if you can run it with dynamorio only?
We want to know if it is a DynamoRIO problem or Dr.Memory problem.
--
Interested in Yoga? Be careful of The Yoga Cult or The Scary Yoga Obsession.
More information from Lorie Anderson and Rick Ross.

tjw...@gmail.com

unread,
Jan 11, 2013, 2:56:38 PM1/11/13
to drmemor...@googlegroups.com
what command line should I use?

tjw...@gmail.com

unread,
Jan 11, 2013, 2:57:02 PM1/11/13
to drmemor...@googlegroups.com
what command line should I use?


On Friday, January 11, 2013 2:50:55 PM UTC-5, Qin Zhao wrote:

tjw...@gmail.com

unread,
Jan 11, 2013, 3:00:07 PM1/11/13
to drmemor...@googlegroups.com
if this is how I'm supposed to run it, it warns about lib64 even though I am 32 bit.  notepad appears but immediately shows the "Notepad has stopped working" dialog.


D:\tools\drmemory\dynamorio\bin32>drrun -verbose -32 C:\Windows\notepad.exe
INFO: targeting application: "C:\Windows\notepad.exe"
INFO: app cmdline:  "C:\Windows\notepad.exe"
INFO: created child with pid 6180 for C:\Windows\notepad.exe
WARNING: cannot find D:\tools\drmemory\dynamorio/lib64\drpreinject.dll: is this
an incomplete installation?
WARNING: cannot find D:\tools\drmemory\dynamorio/lib64\release\dynamorio.dll: is
 this an incomplete installation?
WARNING: cannot find D:\tools\drmemory\dynamorio/lib64\debug\dynamorio.dll: is t
his an incomplete installation?
WARNING: D:\tools\drmemory\dynamorio does not appear to be a valid DynamoRIO roo
t
INFO: waiting forever for app to exit...

Qin Zhao

unread,
Jan 11, 2013, 5:35:46 PM1/11/13
to drmemor...@googlegroups.com
The warning is fine, because DR can run on both 64-bit and 32-bit, while Dr.Memory only runs on 32-bit, so it has only 32-bit drrun in the package.

D:\src\tmp\dynamorio\bin32>drrun -verbose  -- notepad.exe
INFO: targeting application: "C:\Windows\system32\notepad.exe"
INFO: app cmdline:  "notepad.exe"
INFO: created child with pid 8052 for C:\Windows\system32\notepad.exe
WARNING: cannot find D:\src\tmp\dynamorio/lib64\drpreinject.dll: is this an incomplete installation?
WARNING: cannot find D:\src\tmp\dynamorio/lib64\release\dynamorio.dll: is this an incomplete installation?
WARNING: cannot find D:\src\tmp\dynamorio/lib64\debug\dynamorio.dll: is this an incomplete installation?
WARNING: D:\src\tmp\dynamorio does not appear to be a valid DynamoRIO root
INFO: waiting forever for app to exit...

The C:\Windows\notepad.exe is 64-bit while the C:\Windows\system32\notepad.exe is 32-bit.


zhaoqin@ZHAOQIN4-W ~/Workspace/DynamoRIO/builds/build_tests/build_debug-internal-32
$ file /cygdrive/c/Windows/notepad
/cygdrive/c/Windows/notepad: PE32+ executable (GUI) x86-64, for MS Windows

zhaoqin@ZHAOQIN4-W ~/Workspace/DynamoRIO/builds/build_tests/build_debug-internal-32
$ file /cygdrive/c/Windows/system32/notepad
/cygdrive/c/Windows/system32/notepad: PE32 executable (GUI) Intel 80386, for MS Windows

Derek Bruening

unread,
Jan 11, 2013, 6:29:16 PM1/11/13
to drmemor...@googlegroups.com
Both Dr. Memory (1.5.1162) and DynamoRIO (4.0.1) work fine for us on a 32-bit Windows 7 machine (32-bit kernel, which we're assuming is what you have) running "C:\Windows\notepad.exe", so there's something unusual about your setup.

Can you check whether this directory exists:

   %USERPROFILE%\dynamorio

If so, can you run this DynamoRIO command:

% bin32/drconfig.exe -verbose  -reg notepad.exe

And verify a file appears in the aforementioned directory?

- Derek

tim...@gmail.com

unread,
Jun 15, 2013, 5:22:16 AM6/15/13
to drmemor...@googlegroups.com
I had a similar problem on Windows 7 64 bits running 32 bits applications with Dr Memory. Command "drmemory.exe -v C:\Windows\System32\Notepad.exe" exited showing the final report and Notepad GUI never appeared.

The problem was Avast 8.0 anti-virus. Disabling Avast "Behavior shield" in "Security" tab solved the problem and I could start Notepad as well as other applications with Dr Memory.
If not already done, could be worth mentioning this potential problem with anti-virus in documentation.

Gabriel

unread,
Nov 20, 2014, 3:17:49 PM11/20/14
to drmemor...@googlegroups.com
Any news about this issue??
 
I have the same problem on Windows 7 running "Dr. Memory version 1.8.0 -- build 8"
 
C:\...\DrMemory-Windows-1.8.0-8\bin>drmemory -v C:\Windows\System32\Notepad.exe
INFO: targeting application: "C:\Windows\System32\Notepad.exe"
INFO: app cmdline: "C:\Windows\System32\Notepad.exe"
INFO: logdir is "C:\...\...\DrMemory-Windows-1.8.0-8\drmemory\logs"
INFO: symcache_dir is "C:\...\DrMemory-Windows-1.8.0-8\drmemory\logs\symcache"
INFO: configuring Notepad.exe pid=11732 dr_ops="-disable_traces -bb_single_restore_prefix -max_bb_instrs 256 -vm_size 256M -no_enable_reset -no_early_inject -logdir 'C:\...\DrMemory-Windows-1.8.0-8\drmemory\logs\dynamorio` "
INFO: configuring client "C:\...\DrMemory-Windows-1.8.0-8\bin\release\drmemorylib.dll" ops="-logdir `C:\...\DrMemory-Windows-1.8.0-8\drmemory\logs` -symcache_dir `C:\...\DrMemory-Windows-1.8.0-8\drmemory\logs\symcache` -lib_blacklist C:\Windows*.d?? -
resfile 11732 "

INFO: waiting for app to exit...
~~Dr.M~~ Dr. Memory version 1.8.0
~~Dr.M~~ Running "C:\Windows\System32\Notepad.exe"
WARNING: unable to locate results file since can't open C:\...\DrMemory-Windows-1.8.0-8\drmemory\logs/resfile.11732: 2
There was likely an early crash, perhaps due to interference from invasive security software.  Try disabling other software.
~~Dr.M~~ WARNING: application exited with abnormal code 0xc0000005
 
However, dynamorio worked fine:
C:\...\DrMemory-Windows-1.8.0-8\dynamorio\bin64>drrun -verbose C:\Windows\notepad.exe

INFO: targeting application: "C:\Windows\notepad.exe"
INFO: app cmdline:  "C:\Windows\notepad.exe"
INFO: created child with pid 14284 for C:\Windows\notepad.exe

INFO: waiting forever for app to exit...
 
and I don't see any installed security software that could cause this problem.
 
Thanks for any advices!!
 

Le vendredi 11 janvier 2013 17:57:37 UTC+1, tjw3000 a écrit :
I'm trying to run the hello world example, but it exits right away and doesn't start notepad.  I'm running Windows 7 32-bit and my command prompt as an administrator.  Any ideas why this happens?  It also fails with the latest release

C:\Program Files\Dr. Memory\bin>drmemory.exe -logdir "." -v C:\Windows\notepad.e
xe
INFO: targeting application: "C:\Windows\notepad.exe"
INFO: app cmdline: "C:\Windows\notepad.exe"
INFO: logdir is "C:\Program Files\Dr. Memory\bin"
INFO: configuring notepad.exe pid=6860 dr_ops="-disable_traces -bb_single_restor
e_prefix -max_bb_instrs 256 "
INFO: configuring client "C:\Program Files\Dr. Memory/bin/release/drmemorylib.dl
l" ops="-logdir `C:\Program Files\Dr. Memory\bin` -resfile 6860 "
INFO: waiting for app to exit...

Derek Bruening

unread,
Nov 21, 2014, 11:00:59 AM11/21/14
to drmemor...@googlegroups.com
Please try the standard debugging steps listed at http://code.google.com/p/drmemory/wiki/Debugging.

As this will not reproduce on our machines, we would need from you a core dump (most easily obtained from windbg as described on the wiki page) or at least a callstack of the crash (by attaching again as described on the wiki page and catching the crash in the debugger) in order to make any progress on diagnosing and trying to solve the issue.



--

---
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.

Reply all
Reply to author
Forward
0 new messages