Task Manager
-
I have both Studio 6 and Studio .NET installed on one machine. I want to be able to attach to either debuggers via Task Manager right click "Debug" context menu item. I have figured out how to modify the "Debug" command for either studio (e.g. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger). However, what I want is to add 2 items to the context menu of Task Manager so that I can choose which debugger I want. I haven't been able to find the location of Task Manager's context menu data in the registry which makes me think that it may not be alterable. Unless someone knows and I have overlooked - which I am hoping is the case. Thanks!
-
I have both Studio 6 and Studio .NET installed on one machine. I want to be able to attach to either debuggers via Task Manager right click "Debug" context menu item. I have figured out how to modify the "Debug" command for either studio (e.g. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger). However, what I want is to add 2 items to the context menu of Task Manager so that I can choose which debugger I want. I haven't been able to find the location of Task Manager's context menu data in the registry which makes me think that it may not be alterable. Unless someone knows and I have overlooked - which I am hoping is the case. Thanks!
Why not a simple EXE that acts as a proxy. Once an attach has been requested, u pop up this exe and from it you have the various choices, and based on the choice, you invoke the correct debugger with the correct command line. Something like : "MSDEV -p procid -e procid" I have to tell you that Studio .NET will nag that he aint the JIT debugger, so a workaround to this problem would be to set it as the JIT debugger then to reactivate yourself as the JIT debugger afterwards. Good luck. Papa while (TRUE) Papa.WillLove ( Bebe ) ;
-
I have both Studio 6 and Studio .NET installed on one machine. I want to be able to attach to either debuggers via Task Manager right click "Debug" context menu item. I have figured out how to modify the "Debug" command for either studio (e.g. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger). However, what I want is to add 2 items to the context menu of Task Manager so that I can choose which debugger I want. I haven't been able to find the location of Task Manager's context menu data in the registry which makes me think that it may not be alterable. Unless someone knows and I have overlooked - which I am hoping is the case. Thanks!
-
Why not a simple EXE that acts as a proxy. Once an attach has been requested, u pop up this exe and from it you have the various choices, and based on the choice, you invoke the correct debugger with the correct command line. Something like : "MSDEV -p procid -e procid" I have to tell you that Studio .NET will nag that he aint the JIT debugger, so a workaround to this problem would be to set it as the JIT debugger then to reactivate yourself as the JIT debugger afterwards. Good luck. Papa while (TRUE) Papa.WillLove ( Bebe ) ;
Thanks for the response and suggestion, but I have successfully launched VC6 Debugger by altering the registry previously mentioned and haven't had a problem with the JIT debugger. If it turns out that I can't add to the context menu, I will pursue your suggestion. Thanks!
-
Thanks for the response and suggestion, but I have successfully launched VC6 Debugger by altering the registry previously mentioned and haven't had a problem with the JIT debugger. If it turns out that I can't add to the context menu, I will pursue your suggestion. Thanks!
Maybe i didnt make it clear, but VC6 would attach happily by just using the command line, VS.NET would nag if he finds out he's not the prefered JIT :) Another choice is like it is suggested in the other post, to attach from within the interface. For me i find it much easier to have a small exe where i can chose directly my debugger for the current problem, would it be VC6 VS.NET, WinDbg, OllyDbg or ... let it crash! Papa while (TRUE) Papa.WillLove ( Bebe ) ;
-
-
Thanks - I am aware of that, but I am falling in line with the adage that "Programmers are lazy." :)
Jnewg5 wrote: Thanks - I am aware of that, but I am falling in line with the adage that "Programmers are lazy." As a lazy programmer myself, I find using the VS.NET menu easier and quicker, but then again it is very rare that I need to debug an app built by VS6. Only got one supported product using it now. Michael CP Blog [^]
-
Jnewg5 wrote: Thanks - I am aware of that, but I am falling in line with the adage that "Programmers are lazy." As a lazy programmer myself, I find using the VS.NET menu easier and quicker, but then again it is very rare that I need to debug an app built by VS6. Only got one supported product using it now. Michael CP Blog [^]
As a lazy programmer myself, i made a small utility that runs in the background, when i press CTRL + F1 it automatically attaches the application i preconfigure it with into the debugger of my choice. This utility also records some macros and send some keystrokes. :) Papa while (TRUE) Papa.WillLove ( Bebe ) ;
-
As a lazy programmer myself, i made a small utility that runs in the background, when i press CTRL + F1 it automatically attaches the application i preconfigure it with into the debugger of my choice. This utility also records some macros and send some keystrokes. :) Papa while (TRUE) Papa.WillLove ( Bebe ) ;
Papa wrote: i made a small utility that runs in the background, when i press CTRL + F1 it automatically attaches the application i preconfigure it with into the debugger of my choice. This utility also records some macros and send some keystrokes. Cool. Have you posted it as an article? Sounds like it might be a useful tool for your fellow CPians. I don't debug many running processes, so it probably wouldn't save me much time but it might help some others. Michael CP Blog [^]
-
Papa wrote: i made a small utility that runs in the background, when i press CTRL + F1 it automatically attaches the application i preconfigure it with into the debugger of my choice. This utility also records some macros and send some keystrokes. Cool. Have you posted it as an article? Sounds like it might be a useful tool for your fellow CPians. I don't debug many running processes, so it probably wouldn't save me much time but it might help some others. Michael CP Blog [^]
Not yet. I guess i will in the near future, but i know it can make my daily tasks easier, cos in order to test our system, we should enter a username password, so just imagine the number of times you enter those X| Papa while (TRUE) Papa.WillLove ( Bebe ) ;