Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Mon, 29 Mar 1999 23:45:20 +0400
From:	Egor Duda <deo AT logos-m DOT ru>
X-Mailer:	The Bat! (v1.029) S/N A0F2A05A
Reply-To:	Egor Duda <deo AT logos-m DOT ru>
Organization:	DEO
Message-ID:	<19989.990329@logos-m.ru>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	calling cygwin1.dll back
Mime-Version:	1.0

Hi!

  I've  got  a problem writing a dll, which is called from cygwin1.dll
and  then  calls  it  back.  Say, test.exe calls cygwin1.dll, it calls
custom.dll, and then custom.dll tries to call memcpy from cygwin1.dll.
All   3   images   has  different  "--image-base"s. I examine the code
and it appears  that  custom.dll  correctly pushes all parameters onto
stack, then makes a does a "call" instruction and get to something like

1: x/i $eip  0x710079b4 <memcpy>:       jmp    *0x7100b104

As  far,  as  i  understand,  it's  a  thunk.  Alas,  it's incorrectly
initialized   --   0x7100b104   contains 0xb124 instead of 0x6100b124.

Any suggestions?

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -