This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
calling cygwin1.dll back
- To: email@example.com
- Subject: calling cygwin1.dll back
- From: Egor Duda <firstname.lastname@example.org>
- Date: Mon, 29 Mar 1999 23:45:20 +0400
- Organization: DEO
- Reply-To: Egor Duda <email@example.com>
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.
Egor. mailto:firstname.lastname@example.org ICQ 5165414 FidoNet 2:5020/496.19
Want to unsubscribe from this list?
Send a message to email@example.com