?
Solved

WinDbg kills my app's process

Posted on 2008-11-09
6
Medium Priority
?
758 Views
Last Modified: 2013-12-04
Hi Experts!  I'm just starting to use WinDbg.  I loaded the program and attached it to my .net Winform app's process.  I noticed that my app was unresponsive.  i exited Windbg and my app's process was killed.  Basically i can't use Windbg because it seems to mess with my app somehow.  Here's a dump of the load information.  Please help!



Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
*** wait with pending attach
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
ModLoad: 013c0000 0141c000   C:\Users\Administrator\Apps\DataUpdater\DataUpdater.exe
ModLoad: 76f90000 770f0000   C:\Windows\SysWOW64\ntdll.dll
ModLoad: 74ff0000 75036000   C:\Windows\system32\mscoree.dll
ModLoad: 768c0000 769d0000   C:\Windows\syswow64\KERNEL32.dll
ModLoad: 751b0000 75276000   C:\Windows\syswow64\ADVAPI32.dll
ModLoad: 75950000 75a40000   C:\Windows\syswow64\RPCRT4.dll
ModLoad: 75140000 751a0000   C:\Windows\syswow64\Secur32.dll
ModLoad: 75800000 75858000   C:\Windows\syswow64\SHLWAPI.dll
ModLoad: 75ad0000 75b60000   C:\Windows\syswow64\GDI32.dll
ModLoad: 756c0000 75790000   C:\Windows\syswow64\USER32.dll
ModLoad: 75330000 753da000   C:\Windows\syswow64\msvcrt.dll
ModLoad: 757a0000 75800000   C:\Windows\system32\IMM32.DLL
ModLoad: 76b20000 76be8000   C:\Windows\syswow64\MSCTF.dll
ModLoad: 768b0000 768b9000   C:\Windows\syswow64\LPK.DLL
ModLoad: 75280000 752fd000   C:\Windows\syswow64\USP10.dll
ModLoad: 74600000 7479e000   C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc\comctl32.dll
ModLoad: 6f960000 6fef0000   C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
ModLoad: 747b0000 7484b000   C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36\MSVCR80.dll
ModLoad: 75b90000 7669f000   C:\Windows\syswow64\shell32.dll
ModLoad: 769d0000 76b14000   C:\Windows\syswow64\ole32.dll
ModLoad: 6e360000 6ee57000   C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\9adb89fa22fd5b4ce433b5aca7fb1b07\mscorlib.ni.dll
ModLoad: 6dbd0000 6e355000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System\aa7926460a336408c8041330ad90929d\System.ni.dll
ModLoad: 72330000 724d5000   C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualBas#\5b3d048d8c003d743ea5e72caf07773a\Microsoft.VisualBasic.ni.dll
ModLoad: 72a10000 72a6b000   C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
ModLoad: 70860000 709e8000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\6978f2e90f13bc720d57fa6895c911e2\System.Drawing.ni.dll
ModLoad: 6b290000 6be6d000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Windows.Forms\9a254c455892c02355ab0ab0f0727c5b\System.Windows.Forms.ni.dll
ModLoad: 73a60000 73b21000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Runtime.Remo#\3736ba3ecac186f9c5d85f01bda2be98\System.Runtime.Remoting.ni.dll
ModLoad: 75b60000 75b8d000   C:\Windows\syswow64\ws2_32.dll
ModLoad: 751a0000 751a6000   C:\Windows\syswow64\NSI.dll
ModLoad: 74470000 744ab000   C:\Windows\system32\mswsock.dll
ModLoad: 744d0000 744d5000   C:\Windows\system32\wshtcpip.dll
ModLoad: 744e0000 744e5000   C:\Windows\System32\wship6.dll
ModLoad: 70760000 70851000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\cb4cb21d14767292e079366a5d3d76cd\System.Configuration.ni.dll
ModLoad: 6f420000 6f956000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\36f3953f24d4f0b767bf172331ad6f3e\System.Xml.ni.dll
ModLoad: 748a0000 748db000   C:\Windows\system32\rsaenh.dll
ModLoad: 74d50000 74dd0000   C:\Windows\system32\uxtheme.dll
ModLoad: 73bb0000 73bf6000   C:\Users\Administrator\Apps\DataUpdater\log4net.dll
ModLoad: 750c0000 750c8000   C:\Windows\system32\VERSION.dll
ModLoad: 717f0000 71a24000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Core\4cb01a1063e99bd543ca34547e28bd44\System.Core.ni.dll
ModLoad: 739f0000 73a56000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml.Linq\d63d00204d84b8b02b118857e8a59055\System.Xml.Linq.ni.dll
ModLoad: 75a40000 75acd000   C:\Windows\syswow64\oleaut32.dll
ModLoad: 73c00000 73dab000   C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6001.18065_none_9e7abe2ec9c13222\gdiplus.dll
ModLoad: 75050000 7506a000   C:\Users\Administrator\Apps\DataUpdater\WFCShared.dll
ModLoad: 75080000 75088000   C:\Users\Administrator\Apps\DataUpdater\SmtpClientSmtpAppender.dll
ModLoad: 74340000 74345000   C:\Windows\system32\shfolder.dll
ModLoad: 72b00000 72b21000   C:\Windows\system32\NTMARTA.DLL
ModLoad: 75860000 758aa000   C:\Windows\syswow64\WLDAP32.dll
ModLoad: 75940000 75947000   C:\Windows\syswow64\PSAPI.DLL
ModLoad: 72a70000 72a81000   C:\Windows\system32\SAMLIB.dll
ModLoad: 67a80000 68b06000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.ServiceModel\8916ab751fafa7245dc9dfa6cfac3cfc\System.ServiceModel.ni.dll
ModLoad: 75070000 7507c000   C:\Users\Administrator\Apps\DataUpdater\Bukovics.Workflow.Hosting.dll
ModLoad: 71610000 717e5000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Workflow.Run#\5d6b641086cce5fdc858845791bceb39\System.Workflow.Runtime.ni.dll
ModLoad: 6ae30000 6b282000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Workflow.Com#\4ebf9425af71d1715702beddca876205\System.Workflow.ComponentModel.ni.dll
ModLoad: 766f0000 76774000   C:\Windows\syswow64\CLBCatQ.DLL
ModLoad: 739a0000 739e1000   C:\Windows\assembly\NativeImages_v2.0.50727_32\SMDiagnostics\a0cb977cf742634cf54dfe5b81c1b400\SMDiagnostics.ni.dll
ModLoad: 73df0000 73e24000   C:\Users\Administrator\Apps\DataUpdater\ModelWorkflow.dll
ModLoad: 641c0000 64d01000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Web\50ea744ffc3cb7f09b027fd6c5c93b2b\System.Web.ni.dll
ModLoad: 5e3a0000 5e42d000   C:\Windows\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll
ModLoad: 73340000 7336c000   C:\Windows\system32\DNSAPI.dll
ModLoad: 73320000 73328000   C:\Windows\System32\winrnr.dll
ModLoad: 72790000 7279f000   C:\Windows\system32\NLAapi.dll
ModLoad: 72770000 72789000   C:\Windows\system32\IPHLPAPI.DLL
ModLoad: 72730000 72765000   C:\Windows\system32\dhcpcsvc.DLL
ModLoad: 73330000 73337000   C:\Windows\system32\WINNSI.DLL
ModLoad: 72700000 72721000   C:\Windows\system32\dhcpcsvc6.DLL
ModLoad: 726e0000 726ef000   C:\Windows\system32\napinsp.dll
ModLoad: 714c0000 71604000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.WorkflowServ#\88bf6072ecca6a6674cb5f88a903f659\System.WorkflowServices.ni.dll
ModLoad: 705c0000 70757000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.ServiceModel#\dca9222812c379f02e9725de130d13b2\System.ServiceModel.Web.ni.dll
ModLoad: 703f0000 705b5000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Web.Services\1dad08772eb89d48a8a0cfe9b0467eb0\System.Web.Services.ni.dll
ModLoad: 71a50000 71b56000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.IdentityModel\833aa4f13464ecb314a27adbcfca1e22\System.IdentityModel.ni.dll
ModLoad: 74370000 74461000   C:\Windows\system32\crypt32.dll
ModLoad: 744b0000 744c2000   C:\Windows\system32\MSASN1.dll
ModLoad: 74bf0000 74c0e000   C:\Windows\system32\USERENV.dll
ModLoad: 6f040000 6f27e000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Runtime.Seri#\6a0e6b429befa7ae3195cfc8c92ea2cc\System.Runtime.Serialization.ni.dll
ModLoad: 72b30000 72b4b000   C:\Windows\system32\cryptnet.dll
ModLoad: 75040000 75046000   C:\Windows\system32\SensApi.dll
ModLoad: 74300000 7430b000   C:\Windows\system32\httpapi.dll
(13b8.15d8): Break instruction exception - code 80000003 (first chance)
eax=7ef33000 ebx=00000000 ecx=00000000 edx=76ffd2d4 esi=00000000 edi=00000000
eip=76fa0004 esp=0656f9bc ebp=0656f9e8 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\SysWOW64\ntdll.dll - 
ntdll!DbgBreakPoint:
76fa0004 cc              int     3

Open in new window

0
Comment
Question by:sfun28
  • 3
  • 3
6 Comments
 
LVL 86

Expert Comment

by:jkr
ID: 22923611
When you exit WinDbg, the Debuggee will be terminated, that's the standard behaviour.
0
 
LVL 1

Author Comment

by:sfun28
ID: 22924318
maybe i'm using the wrong tool then...is there anyway to attach to an already running process to take a memory dump (checking for memory leaks) without interrupting the running process?  I don't want my app to exit - i just want to examine it in more detail as it runs.
0
 
LVL 86

Expert Comment

by:jkr
ID: 22924440
The problem is Windows' debugging API - there's 'DebugActiveProcess()' (http://msdn.microsoft.com/en-us/library/ms679295.aspx) to attach to a running process, but no counterpart to detach without terminating it, see http://msdn.microsoft.com/en-us/library/ms679303(VS.85).aspx ("Debugging Functions"). As long as you keep WinDbg running, you can still watch your process.
0
[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

 
LVL 1

Author Comment

by:sfun28
ID: 22925796
Got it!  Any suggestion on why the app is unresponsive when the debugger is attached?  I'm happy to keep WinDbg running, but when I attach it to my app, I can't access the main form so i can't perform any operations.  I'd like to use my app while the debugger is attached.
0
 
LVL 86

Accepted Solution

by:
jkr earned 2000 total points
ID: 22925842
I guess WinDbg dy default sets a breakpoint and halts the app - just type 'G' to continue. See also http://www.codeproject.com/KB/debug/windbg_part1.aspx ("Windows Debuggers: Part 1: A WinDbg Tutorial") and http://www.codeproject.com/KB/debug/WinDBGAndSOS.aspx ("Get Started: Debugging Memory Related Issues in .Net Application Using WinDBG and SOS")
0
 
LVL 1

Author Closing Comment

by:sfun28
ID: 31514949
Thanks so much!  You completely answered my question and gave me great resources to help my future efforts.  thanks!!!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows a few slightly more advanced techniques for Windows 7 gadget programming, including how to save and restore user settings for your gadget and how to populate the "details" panel that is displayed in the Windows 7 gadget gallery.  …
After several hours of googling I could not gather any information on this topic. There are several ways of controlling the USB port connected to any storage device. The best example of that is by changing the registry value of "HKEY_LOCAL_MACHINE\S…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question