Ocx breakpoint problem

Ted -- tward@geographix.com
Thursday, February 01, 1996


I created an OCX with AppWizard, and a test app to call it.  My   
breakpoints weren't being hit, so I put in an Int 3, and it stopped.  I   
then did a Run to Cursor, and was asked to resolve the ambiguity for the   
source line.  The debugger was confused about whether to break in   
"GeoImport.ocx" or "GeoImp~1.ocx"  The control is being registered with a   
short file name.

Why is the control being registered with a short file name, and why is   
the debugger getting confused, and how do I prevent this problem?

Thanks for any help.

Ted Ward

tward@geographix.com
Denver, Colorado  

---

Mike Blaszczak -- mikeblas@interserv.com
Saturday, February 03, 1996

On Thu, 1 Feb 1996, "Ward, Ted"  wrote:

>I created an OCX with AppWizard, and a test app to call it.  My   
>breakpoints weren't being hit, so I put in an Int 3, and it stopped.  I   
>then did a Run to Cursor, and was asked to resolve the ambiguity for the   
>source line.  The debugger was confused about whether to break in   
>"GeoImport.ocx" or "GeoImp~1.ocx"  The control is being registered with a   
>short file name.

It turns out that this is the way Win95 OLE works.  I'm not sure if the OLE 
guys decided it was a bug or not, but that's the way it is.

>Why is the control being registered with a short file name, and why is   
>the debugger getting confused, and how do I prevent this problem?

Because it sees the system load the file by the short name, but it knows the 
long file name because of the information in the PDB and/or in the "Extra 
DLLs list" in the "Debug" settings of your project.

I'm pretty sure you can work around the problem by using the short name in 
the "Extra DLLs" list of the IDE.

>Denver, Colorado  

Boy, they're giving the New York Rangers the business today, huh?

.B ekiM
--
TCHAR szLinesman[] = _T("Look!  A skating zebra!");

---

| Вернуться в корень Архива |