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

>>>>> "Paul" == Paul K Gleske <pkg@gleske.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@helixdigital.com -- http://www.helixdigital.com

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

