Hello everyone,
When I use bu or bm to set a breakpoint into a process running C#, there is always error message like – “Operation not supported by
integrated managed debugging.”
How to make WinDbg support .Net application debug?
(I made a search to find some similar questions, but not quite helpful.)
thanks in advance,
George
Windbg is for drivers and services running as services. You can test most
of the service code by running as a normal application without all the
headaches of windbg. Managed code debugging has been designed to work with
Visual Studio. I prefer to use the best tool for the job. If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
Just out of interest, if (in the unlikely instance) that you debug the local
kernel using windbg, you will be unable to attach a Visual Studio 2008
ASP.NET debugger at the same time, I’m not sure if it’s the same case for
debugging a forms application… (VS will tell you that a kernel debugger is
attached/running (I can’t remember which - it’s late here)).
After you perform local debugging and reboot without the debug switch, you
may yet experience problems afterwards with the ASP.NET debugger, this has
been my experience in recent weeks, after working with kernel debugging
locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and then
going back to re-develop some parts of my website in ASP.NET, and forgetting
to reboot the machine in non-debug mode.
Crispin.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
Sent: Sunday, July 06, 2008 22:26
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services. You can test most
of the service code by running as a normal application without all the
headaches of windbg. Managed code debugging has been designed to work with
Visual Studio. I prefer to use the best tool for the job. If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
To set breakpoints in native code, you can still use bp or bm command,
for example bp kernel32!ReadFile.
To set a breakpoint in managed code, you need SOS extension (SOS.dll).
.loadby sos mscorwks
0:000> !name2ee CliHello CliHello.CliHello.Main
Module: 00a72c24 (CliHello.exe)
Token: 0x06000001
MethodDesc: 00a72fe8
Name: CliHello.CliHello.Main(System.String)
Not JITTED yet. Use !bpmd -md 00a72fe8 to break on run.
0:000> !bpmd -md 00a72fe8
MethodDesc = 00a72fe8
Adding pending breakpoints…
BR, Raymond
Thanks David,
Previously I always use WinDbg to debug native code, now I learned some C# and begin to try it with WinDbg. 
Actually, I am not a WinDbg expert before, and I just do some simple tasks, as monitor threads, see dump files to find where program crashes.
My current issue is, I can not install Visual Studio on the machine which runs my program (because of disk limitation), and I want to debug remotely, so I install a small program – WinDbg on remote machine – so that I can debug remotely. Any comments?
regards,
George
----- Original Message ----
From: David Craig
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 5:25:59 AM
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services.? You can test most
of the service code by running as a normal application without all the
headaches of windbg.? Managed code debugging has been designed to work with
Visual Studio.? I prefer to use the best tool for the job.? If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Hi Crispin,
Looks like you are doing something quite fancy! Cool!!
Two more simple questions,
1.
The ASP.Net debugger, do you mean Visual Studio debugger itself?
2.
“reboot the machine in non-debug mode” – I never see any debug mode selection when pressing F8 during system reboot. Could you clarify what do you mean reboot machine in debug mode or non-debug mode please?
regards,
George
----- Original Message ----
From: Crispin Wright
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 6:40:19 AM
Subject: RE: [windbg] WinDbg and C# application
Just out of interest, if (in the unlikely instance) that you debug the local
kernel using windbg, you will be unable to attach a Visual Studio 2008
ASP.NET debugger at the same time, I’m not sure if it’s the same case for
debugging a forms application… (VS will tell you that a kernel debugger is
attached/running (I can’t remember which - it’s late here)).
After you perform local debugging and reboot without the debug switch, you
may yet experience problems afterwards with the ASP.NET debugger, this has
been my experience in recent weeks, after working with kernel debugging
locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and then
going back to re-develop some parts of my website in ASP.NET, and forgetting
to reboot the machine in non-debug mode.
Crispin.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
Sent: Sunday, July 06, 2008 22:26
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services.? You can test most
of the service code by running as a normal application without all the
headaches of windbg.? Managed code debugging has been designed to work with
Visual Studio.? I prefer to use the best tool for the job.? If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thanks BR,
I have tried your solution, here is my output.
0:004> !name2ee TestDebugManaged1.exe TestDebugManaged1.Program.Foo
Module: 0000064280012e20 (TestDebugManaged1.exe)
Seems there is only Module displayed, no method description displayed. What is the root cause?
BTW: name2ee is short for?
regards,
George
----- Original Message ----
From: “Zhang, Raymond”
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 8:44:24 AM
Subject: RE: [windbg] WinDbg and C# application
To set breakpoints in native code, you can still use bp or bm command,
for example? bp kernel32!ReadFile.
To set a breakpoint in managed code, you need SOS extension (SOS.dll).
.loadby sos mscorwks
0:000> !name2ee CliHello CliHello.CliHello.Main
Module: 00a72c24 (CliHello.exe)
Token: 0x06000001
MethodDesc: 00a72fe8
Name: CliHello.CliHello.Main(System.String)
Not JITTED yet. Use !bpmd -md 00a72fe8 to break on run.
0:000> !bpmd -md 00a72fe8
MethodDesc = 00a72fe8
Adding pending breakpoints…
BR, Raymond
—
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
My only suggestion is to upgrade the hard drive. There are just no ways to
do your job with inadequate tools.
“Lin George” wrote in message
news:xxxxx@windbg…
Thanks David,
Previously I always use WinDbg to debug native code, now I learned some C#
and begin to try it with WinDbg.
Actually, I am not a WinDbg expert before, and I just do some simple tasks,
as monitor threads, see dump files to find where program crashes.
My current issue is, I can not install Visual Studio on the machine which
runs my program (because of disk limitation), and I want to debug remotely,
so I install a small program – WinDbg on remote machine – so that I can
debug remotely. Any comments?
regards,
George
----- Original Message ----
From: David Craig
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 5:25:59 AM
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services. You can test most
of the service code by running as a normal application without all the
headaches of windbg. Managed code debugging has been designed to work with
Visual Studio. I prefer to use the best tool for the job. If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thanks David!
Another concern which I do not install Visual Studio on remote machine is, installing Visual Studio on target machine will make the environment not clean, e.g. Visual Studio will install a lot of DLLs, e.g. MFC GUI dlls on the remote machine, and once I met with one issue is my installation script is wrong – forget to copy one DLL, but since I installed the Visual Studio on target machine, it blocks me from finding the wrong script.
Any comments?
regards,
George
----- Original Message ----
From: David Craig
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 9:21:29 AM
Subject: Re:[windbg] WinDbg and C# application
My only suggestion is to upgrade the hard drive.? There are just no ways to
do your job with inadequate tools.
“Lin George” wrote in message
news:xxxxx@windbg…
Thanks David,
Previously I always use WinDbg to debug native code, now I learned some C#
and begin to try it with WinDbg.
Actually, I am not a WinDbg expert before, and I just do some simple tasks,
as monitor threads, see dump files to find where program crashes.
My current issue is, I can not install Visual Studio on the machine which
runs my program (because of disk limitation), and I want to debug remotely,
so I install a small program – WinDbg on remote machine – so that I can
debug remotely. Any comments?
regards,
George
----- Original Message ----
From: David Craig
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 5:25:59 AM
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services. You can test most
of the service code by running as a normal application without all the
headaches of windbg. Managed code debugging has been designed to work with
Visual Studio. I prefer to use the best tool for the job. If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Humm… can’t imagine why you would even need to debug managed code. Since
you don’t have any memory leaks, crash or deadlocks :–).
In any event, Windbg will work. Track down a copy of:
Debugging Microsoft .NET 2.0 Applications
or
Debugging Applications for Microsoft .NET and Microsoft Windows
Both by John Robbins. He specifically covers .NET debugging using windbg.
You can pick them used on Amazon.
Also Advanced Windows Debugging - a very excellent treatment of windbg and
general debugging technique.
I don’t do managed code, but I do use windbg for user mode debugging, and it
is every bit as good as VS. In some ways better.
You just have to learn how to use it - not for your point and click dev.
On Sun, Jul 6, 2008 at 9:18 PM, Lin George
wrote:
> Hi Crispin,
> Looks like you are doing something quite fancy! Cool!!
> Two more simple questions,
> 1.
>
> The ASP.Net debugger, do you mean Visual Studio debugger itself?
> 2.
> “reboot the machine in non-debug mode” – I never see any debug mode
> selection when pressing F8 during system reboot. Could you clarify what do
> you mean reboot machine in debug mode or non-debug mode please?
> regards,
> George
>
>
> ----- Original Message ----
> From: Crispin Wright
> To: Kernel Debugging Interest List
> Sent: Monday, July 7, 2008 6:40:19 AM
> Subject: RE: [windbg] WinDbg and C# application
>
> Just out of interest, if (in the unlikely instance) that you debug the
> local
> kernel using windbg, you will be unable to attach a Visual Studio 2008
> ASP.NET debugger at the same time, I’m not sure if it’s the same case for
> debugging a forms application… (VS will tell you that a kernel debugger is
> attached/running (I can’t remember which - it’s late here)).
>
> After you perform local debugging and reboot without the debug switch, you
> may yet experience problems afterwards with the ASP.NET debugger, this has
> been my experience in recent weeks, after working with kernel debugging
> locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and
> then
> going back to re-develop some parts of my website in ASP.NET, and
> forgetting
> to reboot the machine in non-debug mode.
>
> Crispin.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
> Sent: Sunday, July 06, 2008 22:26
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] WinDbg and C# application
>
> Windbg is for drivers and services running as services. You can test most
> of the service code by running as a normal application without all the
> headaches of windbg. Managed code debugging has been designed to work with
> Visual Studio. I prefer to use the best tool for the job. If you need to
> debug managed code and a service and a driver at once, use both debuggers.
> It is possible, I hear but I don’t write managed code and hope I never have
> to do so.
>
> “Lin George” wrote in message
> news:xxxxx@windbg…
> > Hello everyone,
> >
> > When I use bu or bm to set a breakpoint into a process running C#, there
> > is always error message like – “Operation not supported by
> > integrated managed debugging.”
> > How to make WinDbg support .Net application debug?
> > (I made a search to find some similar questions, but not quite helpful.)
> >
> > thanks in advance,
> > George
> >
> >
> >
> >
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
> Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3244 (20080705)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature
> database 3244 (20080705)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@yahoo.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
>
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Hi Jim,
Thanks for your great comments! I have found some other solutions by using Visual Studio remote debugging. Any comments? Will it work better than using WinDbg?
regards,
George
----- Original Message ----
From: Jim Donelson
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 9:43:54 AM
Subject: Re: [windbg] WinDbg and C# application
Humm… can’t imagine why you would even need to debug managed code. Since you don’t have any memory leaks, crash or deadlocks :–).
In any event, Windbg will work. Track down a copy of:
Debugging Microsoft .NET 2.0 Applications
or
Debugging Applications for Microsoft .NET and Microsoft Windows
Both by John Robbins. He specifically covers .NET debugging using? windbg.
You can pick them used on Amazon.
Also Advanced Windows Debugging - a very excellent treatment of windbg and general debugging technique.
I don’t do managed code, but I do use windbg for user mode debugging, and it is every bit as good as VS. In some ways better.
You just have to learn how to use it - not for your point and click dev.
On Sun, Jul 6, 2008 at 9:18 PM, Lin George wrote:
Hi Crispin,
Looks like you are doing something quite fancy! Cool!!
Two more simple questions,
1.
The ASP.Net debugger, do you mean Visual Studio debugger itself?
2.
“reboot the machine in non-debug mode” – I never see any debug mode selection when pressing F8 during system reboot. Could you clarify what do you mean reboot machine in debug mode or non-debug mode please?
regards,
George
----- Original Message ----
From: Crispin Wright
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 6:40:19 AM
Subject: RE: [windbg] WinDbg and C# application
Just out of interest, if (in the unlikely instance) that you debug the local
kernel using windbg, you will be unable to attach a Visual Studio 2008
ASP.NET debugger at the same time, I’m not sure if it’s the same case for
debugging a forms application… (VS will tell you that a kernel debugger is
attached/running (I can’t remember which - it’s late here)).
After you perform local debugging and reboot without the debug switch, you
may yet experience problems afterwards with the ASP.NET debugger, this has
been my experience in recent weeks, after working with kernel debugging
locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and then
going back to re-develop some parts of my website in ASP.NET, and forgetting
to reboot the machine in non-debug mode.
Crispin.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
Sent: Sunday, July 06, 2008 22:26
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services.? You can test most
of the service code by running as a normal application without all the
headaches of windbg.? Managed code debugging has been designed to work with
Visual Studio.? I prefer to use the best tool for the job.? If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com
Substantially.
You use the VS remote tool - msvcmon or something like that on the target,
and you connect to it remotely with VS. Debugging managed code with some
tool other than VS is generally a silly idea.
Thanks,
Brian Desmond
xxxxx@briandesmond.com
c - 312.731.3132
On Sun, Jul 6, 2008 at 8:57 PM, Lin George
wrote:
> Hi Jim,
>
>
> Thanks for your great comments! I have found some other solutions by using
> Visual Studio remote debugging. Any comments? Will it work better than using
> WinDbg?
>
> regards,
> George
>
> ----- Original Message ----
> From: Jim Donelson
> To: Kernel Debugging Interest List
> Sent: Monday, July 7, 2008 9:43:54 AM
> Subject: Re: [windbg] WinDbg and C# application
>
>
> Humm… can’t imagine why you would even need to debug managed code. Since
> you don’t have any memory leaks, crash or deadlocks :–).
>
> In any event, Windbg will work. Track down a copy of:
> Debugging Microsoft .NET 2.0 Applications
> or
> Debugging Applications for Microsoft .NET and Microsoft Windows
> Both by John Robbins. He specifically covers .NET debugging using windbg.
> You can pick them used on Amazon.
>
> Also Advanced Windows Debugging - a very excellent treatment of windbg and
> general debugging technique.
>
> I don’t do managed code, but I do use windbg for user mode debugging, and
> it is every bit as good as VS. In some ways better.
> You just have to learn how to use it - not for your point and click dev.
>
>
> On Sun, Jul 6, 2008 at 9:18 PM, Lin George
> wrote:
>
>> Hi Crispin,
>> Looks like you are doing something quite fancy! Cool!!
>> Two more simple questions,
>> 1.
>>
>> The ASP.Net debugger, do you mean Visual Studio debugger itself?
>> 2.
>> “reboot the machine in non-debug mode” – I never see any debug mode
>> selection when pressing F8 during system reboot. Could you clarify what do
>> you mean reboot machine in debug mode or non-debug mode please?
>> regards,
>> George
>>
>>
>> ----- Original Message ----
>> From: Crispin Wright
>> To: Kernel Debugging Interest List
>> Sent: Monday, July 7, 2008 6:40:19 AM
>> Subject: RE: [windbg] WinDbg and C# application
>>
>> Just out of interest, if (in the unlikely instance) that you debug the
>> local
>> kernel using windbg, you will be unable to attach a Visual Studio 2008
>> ASP.NET http:</http:> debugger at the same time, I’m not sure if it’s
>> the same case for
>> debugging a forms application… (VS will tell you that a kernel debugger
>> is
>> attached/running (I can’t remember which - it’s late here)).
>>
>> After you perform local debugging and reboot without the debug switch, you
>> may yet experience problems afterwards with the ASP.NET http:</http:>debugger, this has
>> been my experience in recent weeks, after working with kernel debugging
>> locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and
>> then
>> going back to re-develop some parts of my website in ASP.NEThttp:</http:>,
>> and forgetting
>> to reboot the machine in non-debug mode.
>>
>> Crispin.
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
>> Sent: Sunday, July 06, 2008 22:26
>> To: Kernel Debugging Interest List
>> Subject: Re:[windbg] WinDbg and C# application
>>
>> Windbg is for drivers and services running as services. You can test most
>> of the service code by running as a normal application without all the
>> headaches of windbg. Managed code debugging has been designed to work
>> with
>> Visual Studio. I prefer to use the best tool for the job. If you need to
>> debug managed code and a service and a driver at once, use both debuggers.
>> It is possible, I hear but I don’t write managed code and hope I never
>> have
>> to do so.
>>
>> “Lin George” wrote in message
>> news:xxxxx@windbg…
>> > Hello everyone,
>> >
>> > When I use bu or bm to set a breakpoint into a process running C#, there
>> > is always error message like – “Operation not supported by
>> > integrated managed debugging.”
>> > How to make WinDbg support .Net application debug?
>> > (I made a search to find some similar questions, but not quite helpful.)
>> >
>> > thanks in advance,
>> > George
>> >
>> >
>> >
>> >
>>
>>
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature
>> database 3244 (20080705)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature
>> database 3244 (20080705)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@yahoo.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>>
>>
>> —
>> You are currently subscribed to windbg as: unknown lmsubst tag argument:
>> ‘’
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>
> — You are currently subscribed to windbg as: xxxxx@yahoo.comTo unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
> —
> You are currently subscribed to windbg as: xxxxx@briandesmond.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Thanks Brian,
I have setup environment for the remote bugger for Visual Studio, looke cool!
And in your comments, WinDbg have some limitations for debugging managed code compared with Visual Studio remote debugger?
regards,
George
----- Original Message ----
From: Brian Desmond
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 11:33:54 AM
Subject: Re: [windbg] WinDbg and C# application
Substantially.
?
You use the VS remote tool - msvcmon or something like that on the target, and you connect to it remotely with VS. Debugging managed code with some tool other than VS is generally a silly idea.
Thanks,
Brian Desmond
xxxxx@briandesmond.com
c - 312.731.3132
On Sun, Jul 6, 2008 at 8:57 PM, Lin George wrote:
Hi Jim,
?
?
Thanks for your great comments! I have found some other solutions by using Visual Studio remote debugging. Any comments? Will it work better than using WinDbg?
?
regards,
George
----- Original Message ----
From: Jim Donelson
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 9:43:54 AM
Subject: Re: [windbg] WinDbg and C# application
Humm… can’t imagine why you would even need to debug managed code. Since you don’t have any memory leaks, crash or deadlocks :–).
In any event, Windbg will work. Track down a copy of:
Debugging Microsoft .NET 2.0 Applications
or
Debugging Applications for Microsoft .NET and Microsoft Windows
Both by John Robbins. He specifically covers .NET debugging using? windbg.
You can pick them used on Amazon.
Also Advanced Windows Debugging - a very excellent treatment of windbg and general debugging technique.
I don’t do managed code, but I do use windbg for user mode debugging, and it is every bit as good as VS. In some ways better.
You just have to learn how to use it - not for your point and click dev.
On Sun, Jul 6, 2008 at 9:18 PM, Lin George wrote:
Hi Crispin,
Looks like you are doing something quite fancy! Cool!!
Two more simple questions,
1.
The ASP.Net debugger, do you mean Visual Studio debugger itself?
2.
“reboot the machine in non-debug mode” – I never see any debug mode selection when pressing F8 during system reboot. Could you clarify what do you mean reboot machine in debug mode or non-debug mode please?
regards,
George
----- Original Message ----
From: Crispin Wright
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 6:40:19 AM
Subject: RE: [windbg] WinDbg and C# application
Just out of interest, if (in the unlikely instance) that you debug the local
kernel using windbg, you will be unable to attach a Visual Studio 2008
ASP.NET debugger at the same time, I’m not sure if it’s the same case for
debugging a forms application… (VS will tell you that a kernel debugger is
attached/running (I can’t remember which - it’s late here)).
After you perform local debugging and reboot without the debug switch, you
may yet experience problems afterwards with the ASP.NET debugger, this has
been my experience in recent weeks, after working with kernel debugging
locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and then
going back to re-develop some parts of my website in ASP.NET, and forgetting
to reboot the machine in non-debug mode.
Crispin.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
Sent: Sunday, July 06, 2008 22:26
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services.? You can test most
of the service code by running as a normal application without all the
headaches of windbg.? Managed code debugging has been designed to work with
Visual Studio.? I prefer to use the best tool for the job.? If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@briandesmond.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com
I think you’ll discover once you start using VS to debug mnaged code that
limtiatons is a severe understatement.
Thanks,
Brian Desmond
xxxxx@briandesmond.com
c - 312.731.3132
On Sun, Jul 6, 2008 at 10:45 PM, Lin George
wrote:
> Thanks Brian,
>
>
> I have setup environment for the remote bugger for Visual Studio, looke
> cool!
>
> And in your comments, WinDbg have some limitations for debugging managed
> code compared with Visual Studio remote debugger?
>
>
> regards,
> George
>
> ----- Original Message ----
> From: Brian Desmond
> To: Kernel Debugging Interest List
> Sent: Monday, July 7, 2008 11:33:54 AM
> Subject: Re: [windbg] WinDbg and C# application
>
> Substantially.
>
> You use the VS remote tool - msvcmon or something like that on the target,
> and you connect to it remotely with VS. Debugging managed code with some
> tool other than VS is generally a silly idea.
>
> Thanks,
> Brian Desmond
> xxxxx@briandesmond.com
>
> c - 312.731.3132
>
> On Sun, Jul 6, 2008 at 8:57 PM, Lin George
> wrote:
>
>> Hi Jim,
>>
>>
>> Thanks for your great comments! I have found some other solutions by using
>> Visual Studio remote debugging. Any comments? Will it work better than using
>> WinDbg?
>>
>> regards,
>> George
>>
>> ----- Original Message ----
>> From: Jim Donelson
>> To: Kernel Debugging Interest List
>> Sent: Monday, July 7, 2008 9:43:54 AM
>> Subject: Re: [windbg] WinDbg and C# application
>>
>>
>> Humm… can’t imagine why you would even need to debug managed code. Since
>> you don’t have any memory leaks, crash or deadlocks :–).
>>
>> In any event, Windbg will work. Track down a copy of:
>> Debugging Microsoft .NET 2.0 Applications
>> or
>> Debugging Applications for Microsoft .NET and Microsoft Windows
>> Both by John Robbins. He specifically covers .NET debugging using windbg.
>> You can pick them used on Amazon.
>>
>> Also Advanced Windows Debugging - a very excellent treatment of windbg and
>> general debugging technique.
>>
>> I don’t do managed code, but I do use windbg for user mode debugging, and
>> it is every bit as good as VS. In some ways better.
>> You just have to learn how to use it - not for your point and click dev.
>>
>>
>> On Sun, Jul 6, 2008 at 9:18 PM, Lin George
>> wrote:
>>
>>> Hi Crispin,
>>> Looks like you are doing something quite fancy! Cool!!
>>> Two more simple questions,
>>> 1.
>>>
>>> The ASP.Net debugger, do you mean Visual Studio debugger itself?
>>> 2.
>>> “reboot the machine in non-debug mode” – I never see any debug mode
>>> selection when pressing F8 during system reboot. Could you clarify what do
>>> you mean reboot machine in debug mode or non-debug mode please?
>>> regards,
>>> George
>>>
>>>
>>> ----- Original Message ----
>>> From: Crispin Wright
>>> To: Kernel Debugging Interest List
>>> Sent: Monday, July 7, 2008 6:40:19 AM
>>> Subject: RE: [windbg] WinDbg and C# application
>>>
>>> Just out of interest, if (in the unlikely instance) that you debug the
>>> local
>>> kernel using windbg, you will be unable to attach a Visual Studio 2008
>>> ASP.NET http:</http:> debugger at the same time, I’m not sure if
>>> it’s the same case for
>>> debugging a forms application… (VS will tell you that a kernel debugger
>>> is
>>> attached/running (I can’t remember which - it’s late here)).
>>>
>>> After you perform local debugging and reboot without the debug switch,
>>> you
>>> may yet experience problems afterwards with the ASP.NEThttp:</http:>debugger, this has
>>> been my experience in recent weeks, after working with kernel debugging
>>> locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and
>>> then
>>> going back to re-develop some parts of my website in ASP.NEThttp:</http:>,
>>> and forgetting
>>> to reboot the machine in non-debug mode.
>>>
>>> Crispin.
>>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com
>>> [mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
>>> Sent: Sunday, July 06, 2008 22:26
>>> To: Kernel Debugging Interest List
>>> Subject: Re:[windbg] WinDbg and C# application
>>>
>>> Windbg is for drivers and services running as services. You can test
>>> most
>>> of the service code by running as a normal application without all the
>>> headaches of windbg. Managed code debugging has been designed to work
>>> with
>>> Visual Studio. I prefer to use the best tool for the job. If you need
>>> to
>>> debug managed code and a service and a driver at once, use both
>>> debuggers.
>>> It is possible, I hear but I don’t write managed code and hope I never
>>> have
>>> to do so.
>>>
>>> “Lin George” wrote in message
>>> news:xxxxx@windbg…
>>> > Hello everyone,
>>> >
>>> > When I use bu or bm to set a breakpoint into a process running C#,
>>> there
>>> > is always error message like – “Operation not supported by
>>> > integrated managed debugging.”
>>> > How to make WinDbg support .Net application debug?
>>> > (I made a search to find some similar questions, but not quite
>>> helpful.)
>>> >
>>> > thanks in advance,
>>> > George
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>> —
>>> You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
>>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>>
>>> Information from ESET NOD32 Antivirus, version of virus
>>> signature
>>> database 3244 (20080705)
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>> Information from ESET NOD32 Antivirus, version of virus
>>> signature
>>> database 3244 (20080705)
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>> —
>>> You are currently subscribed to windbg as: xxxxx@yahoo.com
>>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>>
>>>
>>>
>>>
>>>
>>> —
>>> You are currently subscribed to windbg as: unknown lmsubst tag argument:
>>> ‘’
>>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>>
>>
>> — You are currently subscribed to windbg as: xxxxx@yahoo.comTo unsubscribe send a blank email to
>> xxxxx@lists.osr.com
>>
>>
>> —
>> You are currently subscribed to windbg as: xxxxx@briandesmond.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>
> — You are currently subscribed to windbg as: xxxxx@yahoo.comTo unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
Thanks Brain,
I am enjoying debugging by Visual Studio remote debugger. Sorry that my English is not very good, could you clarify what do you mean “limtiatons is a severe understatement”, say in some other words?
regards,
George
----- Original Message ----
From: Brian Desmond
To: Kernel Debugging Interest List
Cc: xxxxx@lists.osr.com
Sent: Monday, July 7, 2008 2:46:26 PM
Subject: Re: [windbg] WinDbg and C# application
I think you’ll discover once you start using VS to debug mnaged code that limtiatons is a severe understatement.
?
Thanks,
Brian Desmond
xxxxx@briandesmond.com
c - 312.731.3132
On Sun, Jul 6, 2008 at 10:45 PM, Lin George wrote:
Thanks Brian,
?
?
I have setup environment for the remote bugger for Visual Studio, looke cool!
?
And in your comments, WinDbg have some limitations for debugging managed code compared with Visual Studio remote debugger?
?
?
regards,
George
----- Original Message ----
From: Brian Desmond
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 11:33:54 AM
Subject: Re: [windbg] WinDbg and C# application
Substantially.
?
You use the VS remote tool - msvcmon or something like that on the target, and you connect to it remotely with VS. Debugging managed code with some tool other than VS is generally a silly idea.
Thanks,
Brian Desmond
xxxxx@briandesmond.com
c - 312.731.3132
On Sun, Jul 6, 2008 at 8:57 PM, Lin George wrote:
Hi Jim,
?
?
Thanks for your great comments! I have found some other solutions by using Visual Studio remote debugging. Any comments? Will it work better than using WinDbg?
?
regards,
George
----- Original Message ----
From: Jim Donelson
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 9:43:54 AM
Subject: Re: [windbg] WinDbg and C# application
Humm… can’t imagine why you would even need to debug managed code. Since you don’t have any memory leaks, crash or deadlocks :–).
In any event, Windbg will work. Track down a copy of:
Debugging Microsoft .NET 2.0 Applications
or
Debugging Applications for Microsoft .NET and Microsoft Windows
Both by John Robbins. He specifically covers .NET debugging using? windbg.
You can pick them used on Amazon.
Also Advanced Windows Debugging - a very excellent treatment of windbg and general debugging technique.
I don’t do managed code, but I do use windbg for user mode debugging, and it is every bit as good as VS. In some ways better.
You just have to learn how to use it - not for your point and click dev.
On Sun, Jul 6, 2008 at 9:18 PM, Lin George wrote:
Hi Crispin,
Looks like you are doing something quite fancy! Cool!!
Two more simple questions,
1.
The ASP.Net debugger, do you mean Visual Studio debugger itself?
2.
“reboot the machine in non-debug mode” – I never see any debug mode selection when pressing F8 during system reboot. Could you clarify what do you mean reboot machine in debug mode or non-debug mode please?
regards,
George
----- Original Message ----
From: Crispin Wright
To: Kernel Debugging Interest List
Sent: Monday, July 7, 2008 6:40:19 AM
Subject: RE: [windbg] WinDbg and C# application
Just out of interest, if (in the unlikely instance) that you debug the local
kernel using windbg, you will be unable to attach a Visual Studio 2008
ASP.NET debugger at the same time, I’m not sure if it’s the same case for
debugging a forms application… (VS will tell you that a kernel debugger is
attached/running (I can’t remember which - it’s late here)).
After you perform local debugging and reboot without the debug switch, you
may yet experience problems afterwards with the ASP.NET debugger, this has
been my experience in recent weeks, after working with kernel debugging
locally (on both Vista x86 Free, and Windows Server 2008 x64 Free), and then
going back to re-develop some parts of my website in ASP.NET, and forgetting
to reboot the machine in non-debug mode.
Crispin.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Craig
Sent: Sunday, July 06, 2008 22:26
To: Kernel Debugging Interest List
Subject: Re:[windbg] WinDbg and C# application
Windbg is for drivers and services running as services.? You can test most
of the service code by running as a normal application without all the
headaches of windbg.? Managed code debugging has been designed to work with
Visual Studio.? I prefer to use the best tool for the job.? If you need to
debug managed code and a service and a driver at once, use both debuggers.
It is possible, I hear but I don’t write managed code and hope I never have
to do so.
“Lin George” wrote in message
news:xxxxx@windbg…
> Hello everyone,
>
> When I use bu or bm to set a breakpoint into a process running C#, there
> is always error message like – “Operation not supported by
> integrated managed debugging.”
> How to make WinDbg support .Net application debug?
> (I made a search to find some similar questions, but not quite helpful.)
>
> thanks in advance,
> George
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@blocksoft.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature
database 3244 (20080705)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
—
You are currently subscribed to windbg as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@briandesmond.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com