Very Strange Happenings (Solution)

Erik Funkenbusch -- chucks@skypoint.com
Friday, January 26, 1996

Well, I believe i've solved my own problem before it even managed to
get approved by the moderator.

To Recap: I was experiencing very strange behavior in the class 
initialization of an app, pointers were being overwritten somehow
before any non-mfc code was ever executed.

The problem seems to be that afxdump cannot be used in an extension
DLL.  This was causing a lot of headaches that were next to impossible
to track down (it took almost a week of analyzing assembly to figure
it out).

Thanks for any help anyone might give before reading this solution :)

Erik Funkenbusch
System Architect
Clear With Computers
chucks@skypoint.com

---

Mike Blaszczak -- mikeblas@interserv.com
Sunday, January 28, 1996

On Fri, 26 Jan 1996, Erik Funkenbusch  wrote:

>To Recap: I was experiencing very strange behavior in the class 
>initialization of an app, pointers were being overwritten somehow
>before any non-mfc code was ever executed.

I didn't see your original posting, I don't think.  What do you mean by "the 
class initialization of an app"?

>The problem seems to be that afxdump cannot be used in an extension
>DLL.  This was causing a lot of headaches that were next to impossible
>to track down (it took almost a week of analyzing assembly to figure
>it out).

You should be able to use afxdump in an extension DLL without any problems.  
If you try to use afxdump before MFC is initialized (for example, if you try 
to TRACE() in a constructor of a static object), you'll get into trouble.

.B ekiM
--
TCHAR szDisc[] = _T("These words are my own; I do not speak for Microsoft.");

---

Andrea Bioli -- abioli@mbox.vol.it
Monday, January 29, 1996

> >The problem seems to be that afxdump cannot be used in an extension
> >DLL.  This was causing a lot of headaches that were next to impossible
> >to track down (it took almost a week of analyzing assembly to figure
> >it out).
> 
> You should be able to use afxdump in an extension DLL without any problems.  
> If you try to use afxdump before MFC is initialized (for example, if you try 
> to TRACE() in a constructor of a static object), you'll get into trouble.
> 
> .B ekiM

Mike, there is something about this in Tech Note 33 (Visual C++ 1.5) 
under API limitations.

Andrea Bioli
abioli@mbox.vol.it
 

---

Mike Blaszczak -- mikeblas@interserv.com
Wednesday, January 31, 1996

On Mon, 29 Jan 1996, "Andrea Bioli"  wrote:
>> >The problem seems to be that afxdump cannot be used in an extension
>> >DLL.  This was causing a lot of headaches that were next to impossible
>> >to track down (it took almost a week of analyzing assembly to figure
>> >it out).
>> 
>> You should be able to use afxdump in an extension DLL without any
>> problems.  
>> If you try to use afxdump before MFC is initialized (for example, if you 
>> try 
>> to TRACE() in a constructor of a static object), you'll get into trouble.
>> 
>> .B ekiM
>
>Mike, there is something about this in Tech Note 33 (Visual C++ 1.5) 
>under API limitations.

I can't find any such text in the same technote in VC++ 4.0.  Apparently, 
this restriction has been lifted for modern versions of the libraries.

.B ekiM

---

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