🚀 go-pugleaf

I'm developing an app with an Automation Controller (client) written in Borland
C++ Builder 3 & an Automation Server written in Visual C++ 5.  The Server is an
in-process server (DLL).  The Controller calls methods in the Server via vtbl.
I've got one method call from the Controller to the Server working fine.  But
I'm having big problems with the 2nd.  It crashes with a Stack Overllow
exception somewhere between the call in the Controller app & reaching the method
in the Server.  

One thing that makes debugging difficult is that I can't find any way to
simultaneously debug the EXE (in BCB3) & the DLL (in VC5).  So I must debug in
one or the other.

When I debug the EXE, a stack overflow messagebox appears.  The call stack
window doesn't even show the EXE.  From the stack bottom, there are MANY calls
from the same address in the DLL.  Then some other addresses in the DLL.  Then
addresses from various other places including MFC42D.DLL.  But since the
debugger can't read the VC5 symbol table, there's nothing I can do with the
addresses.

When I debug the DLL, starting the EXE in the process, I get a stack overflow
messagebox, but the call stack cannot be displayed.  

Short of somehow debugging COM through disassembled code, there's not much I can
do here.  I've already tried changing how I specify the array (x[] to *x).  I
guess I could get rid of the array just to see if that helps ... but that's a
lot of work.  I've already shrunk the array to miniscule size.

Any suggestions???

=======================================================
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=======================================================