[omniORB] Weekend CORBA blues #2: user breakpoint on String_v ar destructor

jnye@micro-optics.com jnye@micro-optics.com
Sun, 10 Jun 2001 21:22:09 -0300


Have you made sure to use consistent linking (i.e.: dynamic VC++ C library
with dynamic omniORB or static VC++ C library with static omniORB)?

-----Original Message-----
From: owner-omniorb-list@uk.research.att.com
[mailto:owner-omniorb-list@uk.research.att.com]On Behalf Of Bruce
Fountain
Sent: Sunday, June 10, 2001 9:02 PM
To: omniorb-list@uk.research.att.com
Subject: [omniORB] Weekend CORBA blues #2: user breakpoint on String_var
destructor


Here is an odd one...

for some reason, whenever the destructor is called for a CORBA::String_var,
it generates a user breakpoint in my debugger (VC++6 on NT4). The stack
looks like this:


    NTDLL! 77f7629c()
    NTDLL! 77f8c4de()
    NTDLL! 77f7e587()
    NTDLL! 77f64f43()
    MSVCRT! 7800113d()
    operator delete(void * 0x008cbe40) line 7 + 9 bytes
    omni::freeString(char * 0x008cbe40) line 240 + 33 bytes
    _CORBA_String_var::~_CORBA_String_var() line 109 + 11 bytes
    main(int 1, char * * 0x003003a0) line 69
    SERVER! mainCRTStartup + 227 bytes
    KERNEL32! 77f1ba06()

My code couldn't be much simpler:

    int main(int argc, char* argv[])
    {
        {
            CORBA::String_var tr = CORBA::string_dup("foobar");

            // s goes out of scope now
        }
        return 0;
    }

I have never seen this behaviour before and I have no idea what could be
causing it. Perhaps some obscure project setting? Any tips much appreciated,
since this behaviour makes debugging a first class pita.

Oh yes, almost forgot: this only happens for Win32 Console Apps (as
generated by the wizard). MFC AppWizard(exe) projects work fine.

Best regards,

Bruce Fountain
Mi Consulting Group (Australia) Pty Ltd
Direct Line:  +61 (0)8 9368 8607
Switchboard:  +61 (0)8 9368 8600
Facsimile:    +61 (0)8 9368 8699
E-mail: b_fountain@motherwell.com.au