Re: Virtual Table Corruption:

From:

Ulrich Eckhardt <eckhardt@satorlaser.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Wed, 9 Sep 2009 12:42:59 CST

Message-ID:

<kj3kn6-d61.ln1@satorlaser.homedns.org>

Sada wrote:

when I call a C function that is there in staticLib2, from main
project the virtual table of the calling member getting corrupted ,
and what i noticed here is, the " this " pointer become invalid.

I'm not sure what you are doing here. How can any C code even access an
object with a vtable? After all, that requires 'virtual' and
memberfunctions, but C doesn't have those. How are you detecting that
something is broken? What is inside the function that breaks it? Try
reducing the code to the bare minimum that is necessary to reproduce the
problem.

The strange thing here is if i include those C files in main project
instead in staticLib2 it works fine, this time no virtual table
corruption.

Different compiler settings might make a difference, as can many other
discrepancies between the different modules.

Uli

--
Sator Laser GmbH
Gesch??ftsf??hrer: Thorsten F??cking, Amtsgericht Hamburg HR B62 932

[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]