Re: Debugging thru AxHost
- From: "mano" <eg.manoharan@xxxxxxxxx>
- Date: 7 Mar 2007 03:18:38 -0800
On Mar 7, 3:27 pm, "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
wrote:
In VB.NET application, set breakpoint at some place where you absolutely
sure that the ocx will be loaded. After that breakpoint is hit, check the presence
of the ocx and its symbols in Modules window.
I did the above step & the ocx control is loaded and its symbol is al
lodaded.
This is the line I copied from the modules window.
"DebTest.ocx D:\debug test\DebTest.ocx N/A N/A Symbols loaded. D:
\debug test\DebTest.pdb 33 1.00.0.0 3/6/2007 5:28 PM 11000000-11006000
[3172] W.exe: Native "
I have set break point in the ocx also but it is not hiting the break
points of the ocx control.
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?
Oleg- Hide quoted text -
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.
Mano
.
- Follow-Ups:
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- 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
- Debugging thru AxHost
- Prev by Date: Re: Debugging thru AxHost
- Next by Date: Re: Debugging thru AxHost
- Previous by thread: Re: Debugging thru AxHost
- Next by thread: Re: Debugging thru AxHost
- Index(es):
Relevant Pages
|
Loading