Debug and attach to a process
-
i m trying to debug a dll and when i try to attach it to a running process, i don't see any process in the process dialog box WHY? steps: 1: create new dll project 2: do anything..... 3: from the debug menu select start debug option 4: then select attach to process 5: now the process dialog box appears now i have to select a process from the list but on my system i don't see any process in this process dialog. Dev Dev
-
i m trying to debug a dll and when i try to attach it to a running process, i don't see any process in the process dialog box WHY? steps: 1: create new dll project 2: do anything..... 3: from the debug menu select start debug option 4: then select attach to process 5: now the process dialog box appears now i have to select a process from the list but on my system i don't see any process in this process dialog. Dev Dev
deyadav wrote: i don't see any process in this process dialog i have no idea why is that happening but as far as i can remember if you are trying to debug a dll then the process attached should load ur dll explicitly or implicitly only then the DllMain gets called, so make a super simple app which calls LoadLibrary("urdll"); and then in dll project put the exe path Hope it helps :) C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg
-
deyadav wrote: i don't see any process in this process dialog i have no idea why is that happening but as far as i can remember if you are trying to debug a dll then the process attached should load ur dll explicitly or implicitly only then the DllMain gets called, so make a super simple app which calls LoadLibrary("urdll"); and then in dll project put the exe path Hope it helps :) C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg
-
i made a sample application and before i try to debug the dll i run the sample application so that i can select it from the process dialog, but there i don't see anything..... :confused:
after making the dll press f5 to debug it a messagbox will come asking for the location of the exe to load enter the path of the executable in that hope that helps :) C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg
-
after making the dll press f5 to debug it a messagbox will come asking for the location of the exe to load enter the path of the executable in that hope that helps :) C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg
thankx for ur reply but my problem is I DON'T SEE the processes in the process dialog.... Build|Start debug|Attach to process... now in the process dialog all the running processes r there.... but on my system it's blank(not a single process is there)..... YYYYYYY is my question.... do i have to make any settings for this?????? :zzz:
-
thankx for ur reply but my problem is I DON'T SEE the processes in the process dialog.... Build|Start debug|Attach to process... now in the process dialog all the running processes r there.... but on my system it's blank(not a single process is there)..... YYYYYYY is my question.... do i have to make any settings for this?????? :zzz:
This command allows you to attach the debugger into an existing process. It does not allow you to attach your DLL into an existing process. What you need to do is create a simple application that loads your DLL. Then set a breakpoint into the DLL's DllMain function. Now, run the sample application in debug mode, and after the LoadLibrary call, the DllMain's breakpoint gets fired. At least on my computer I was able to attach the debugger into a remote process, break it, run through a set of assembly code lines, and then terminate it. Might it be that you don't have any processes running, or that your user has no rights to see them ? Check CTRL+ALT+DEL and Task Manager. Can you see the processes there ? -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.
-
This command allows you to attach the debugger into an existing process. It does not allow you to attach your DLL into an existing process. What you need to do is create a simple application that loads your DLL. Then set a breakpoint into the DLL's DllMain function. Now, run the sample application in debug mode, and after the LoadLibrary call, the DllMain's breakpoint gets fired. At least on my computer I was able to attach the debugger into a remote process, break it, run through a set of assembly code lines, and then terminate it. Might it be that you don't have any processes running, or that your user has no rights to see them ? Check CTRL+ALT+DEL and Task Manager. Can you see the processes there ? -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.
-
i m trying to debug a dll and when i try to attach it to a running process, i don't see any process in the process dialog box WHY? steps: 1: create new dll project 2: do anything..... 3: from the debug menu select start debug option 4: then select attach to process 5: now the process dialog box appears now i have to select a process from the list but on my system i don't see any process in this process dialog. Dev Dev
If all you want is to debug a DLL, then you're going about it the wrong way. Attaching to a process is used when you want to debug that process. To debug your DLL, you need a program that loads and uses the DLL. When you hit F5 the first time, VC asks you what EXE to run, that's where you tell it the name of the program that will use the DLL. For example, if your DLL were an IE plugin, you would use IE as the program. --Mike-- Personal stuff:: Ericahist | Homepage Shareware stuff:: 1ClickPicGrabber | RightClick-Encrypt CP stuff:: CP SearchBar v2.0.2 | C++ Forum FAQ ---- You cannot truly appreciate Dilbert unless you've read it in the original Klingon.