Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Dario Alcocer 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" Cc: Subject: Re: Issue calling COM function(s) In-Reply-To: References: X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid >>>>> "Paul" == Paul K Gleske 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