Re: Debugging thru AxHost
- From: "mano" <eg.manoharan@xxxxxxxxx>
- Date: 8 Mar 2007 04:19:04 -0800
On Mar 7, 4:44 pm, "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
wrote:
Try to show a message box from the ocx (when it is called by the client app).
While this message box is shown, break into debugger, check the call stack
and switch to a stack frame that belongs to the ocx. Will the debugger be able
to show you the ocx' sources in this case?
Yes in this case the Debugger shows the VB6 ocx source in VB.Net. But
I want step into VB6 Ocx control.
How I have to step into VB6 ocx.
I am not sure it's possible to step between VB.NET and VB6 code in this case,
AFAIR breakpoints always had to be used as a workaround.
Btw, do breakpoints work now? (e.g. if you set breakpoint in the source that has been
shown by the debugger, e.g. in a place that will be executed after you dismiss
the message box)
Oleg
Thanks for your responses and valuable guidence. This is helping me to
debug the ocx control to some extend using the .Net IDE.
Thanks & Regards
Manoharan
.
- References:
- Debugging thru AxHost
- From: Manoharan
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Debugging thru AxHost
- Prev by Date: RE: Can't single-step
- Next by Date: Re: Directory Listing Denied
- Previous by thread: Re: Debugging thru AxHost
- Next by thread: Re: MiniDumpWriteDump fails when using dump type MiniDumpWithIndirectlyReferencedMemory
- Index(es):
Relevant Pages
|
Loading