Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Crash launching wow64 executable

144 views
Skip to first unread message

Davis@discussions.microsoft.com Ian Davis

unread,
Jul 14, 2009, 2:12:02 PM7/14/09
to
My .NET application runs fine on win32, but when running on x64 with wow64,
the application crashes instantly. When trying to debug through VS2008, the
debugger doesn't even attach before the application dies.

I loaded WinDbg x64 and attached to the process starting and I get the
folling error:

-- LuaPriv initialized--
(1120.13f4): Break instruction exception - code 80000003 (first chance)
ntdll!DbgBreakPoint:
00000000`77464ea0 cc int 3
0:000> .sympath+
"srv*c:\mysymbols*http://msdl.microsoft.com/download/symbols;cache*c:\mysymbols"
Symbol search path is:
srv*c:\mysymbols*http://msdl.microsoft.com/download/symbols;cache*c:\mysymbols
0:000> .reload
Reloading current modules
.........................
0:000> g
ModLoad: 00000000`068a0000 00000000`069cc000 WOW64_IMAGE_SECTION
ntdll!ZwTerminateProcess+0xa:
00000000`77465d3a c3 ret
0:000> kb
RetAddr : Args to Child
: Call Site
00000000`75719e02 : 00000000`c0000001 00000000`0007f5c0 00000000`0007e4c8
00000000`0007ece0 : ntdll!ZwTerminateProcess+0xa
00000000`774552d3 : 00000000`00214f00 00000000`00000000 00000000`775361b0
00000000`00000000 : wow64!Wow64LdrpInitialize+0x16a
00000000`77455363 : 00000000`00000000 00000000`00000000 00000000`7efdf000
00000000`77457ca7 : ntdll!LdrpInitializeProcess+0x14ac
00000000`774485ce : 00000000`0007f5c0 00000000`00000000 00000000`7efdf000
00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x1ff19
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000
00000000`00000000 : ntdll!LdrInitializeThunk+0xe

I am completely lost as to why I am getting this error. I have other win32
apps that run just fine under wow64.

Volodymyr M. Shcherbyna

unread,
Jul 14, 2009, 2:47:55 PM7/14/09
to
Ian Davis wrote:

If you have no ideas about the problem, I suggest you to run your
application under Application Verifier with maximum checks and analyze it
while debugging. If App Verifier would no eliminate any issues, the second
option is to put as more as possible logs in application to locate
problematic code.

--
Volodymyr M. Shcherbyna, blog: http://www.shcherbyna.com/
(This posting is provided "AS IS" with no warranties, and confers no rights)

Ian Davis

unread,
Jul 14, 2009, 2:48:01 PM7/14/09
to
Got some help; it turns out the Microsoft Application Verifier was watching
my process and killing the application.

Volodymyr M. Shcherbyna

unread,
Jul 14, 2009, 3:12:09 PM7/14/09
to
Ian Davis wrote:

The best is to run application under debug and verifier, so that you have
nice info in Output window and actually can see what source line is
failing.

John Lan

unread,
Jul 14, 2009, 2:17:35 PM7/14/09
to
it's probably a library dependency issue, use dependency walker (x64
version), or
enable loader snap via gflags.exe to profile process startup.

"Ian Davis" <Ian Da...@discussions.microsoft.com> 写入消息
news:A4711B93-2B27-4C28...@microsoft.com...

0 new messages