Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Dario Alcocer <alcocer AT helixdigital DOT com>
MIME-Version:	1.0
Message-ID:	<15142.35113.679546.114735@coyote.priv.helixdigital.com>
Date:	Tue, 12 Jun 2001 14:27:05 -0700
To:	"Paul K Gleske" <pkg AT gleske DOT org>
Cc:	<cygwin AT cygwin DOT com>
Subject:	Re: Issue calling COM function(s)
In-Reply-To:	<NCBBLNOKDKEGJLPOBEJDMEMKGHAA.pkg@gleske.org>
References:	<NCBBLNOKDKEGJLPOBEJDMEMKGHAA DOT pkg AT gleske DOT org>
X-Mailer:	VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid

>>>>> "Paul" == Paul K Gleske <pkg AT gleske DOT org> writes:

    Paul> I'm having trouble porting a VC++ based windows project to a
    Paul> GCC based project.  Don't ask why, it just is.

    Paul> My issue is one of the first (the first?) COM function I
    Paul> call is CreateStreamFromHGlobal.  This function seems to
    Paul> work, but I get a segv on the first method call on the
    Paul> stream (IStream->Stat).  It seems that the vtable might be
    Paul> wrong.

I was running into the same problem myself.  Make sure you call
CoInitialize() before you issue any COM calls in your program.  It
should clear the memory faults.

Oh, one other thing: you'll need to pass -lole32 to gcc when linking.
Actually, you may need to specify additional Windows libraries
depending on what COM stuff you're calling.

Hope this helps,

-- 
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
alcocer AT helixdigital DOT com -- http://www.helixdigital.com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -