Jason Tishler wrote:
By the way, is it reliable to use objdump -x to find the base
(ImageBase) ? For cygssl-0.9.8.dll it is 1000, but I thought
the base was 0x6300
I use a command line like the following:
$ objdump -p /usr/bin/cygssl-0.9.7.dll | fgrep ImageBase
ImageBase
Gerrit,
On Thu, Jul 07, 2005 at 11:03:01PM +0200, Gerrit P. Haase wrote:
> Gerrit P. Haase wrote:
> >Sounds good. WHat is the magic flag I need to add to the link
> >commands?
>
> Would --enable-auto-image-base do it or do I need to specify an address
> with --image-base ? If the second, which
On Jul 8 19:46, Gerrit P. Haase wrote:
> Corinna Vinschen wrote:
> >What? Why? OpenSSL uses another base address already in the Makefile
> >(0x6300).
>
> Good thing. I had problems using openssl extensions for MySQL and perl
> together (half year back). Is this a recent change or was it on
Corinna Vinschen wrote:
On Jul 8 17:20, Gerrit P. Haase wrote:
Christopher Faylor wrote:
I don't think so but I don't think it will use cygwin's address anyway.
Ok. Maybe Corinna should do the same for openssl?
What? Why? OpenSSL uses another base address already in the Makefile
(0x6
On Jul 8 17:20, Gerrit P. Haase wrote:
> Christopher Faylor wrote:
> >I don't think so but I don't think it will use cygwin's address anyway.
>
> Ok. Maybe Corinna should do the same for openssl?
What? Why? OpenSSL uses another base address already in the Makefile
(0x6300).
Corinna
--
Christopher Faylor wrote:
On Fri, Jul 08, 2005 at 11:51:39AM +0200, Gerrit P. Haase wrote:
Christopher Faylor wrote:
--enable-auto-image-base would probably be sufficient -- at least as a
first stab at fixing this problem. Just make sure that none of the
dlls load into cygwin's load address
On Fri, Jul 08, 2005 at 11:51:39AM +0200, Gerrit P. Haase wrote:
>Christopher Faylor wrote:
>>--enable-auto-image-base would probably be sufficient -- at least as a
>>first stab at fixing this problem. Just make sure that none of the
>>dlls load into cygwin's load address.
>
>Can I tell the linker
Christopher Faylor wrote:
--enable-auto-image-base would probably be sufficient -- at least as a
first stab at fixing this problem. Just make sure that none of the dlls
load into cygwin's load address.
Can I tell the linker to exclude some address?
Gerrit
--
Unsubscribe info: http://c
On Thu, Jul 07, 2005 at 11:03:01PM +0200, Gerrit P. Haase wrote:
>Gerrit P. Haase wrote:
>
>>>Wouldn't this problem be ameliorated slightly if the perl DLLs all
>>>loaded in unique addresses to begin with? Isn't the problem that all
>>>perl DLLs (and probably others) are loading in address 0x1
On Thu, Jul 07, 2005 at 10:45:14PM +0200, Gerrit P. Haase wrote:
>Christopher Faylor wrote:
>
>>On Thu, Jul 07, 2005 at 02:08:40PM -0400, Larry Hall wrote:
>>
>>>At 01:10 PM 7/7/2005, you wrote:
>>>
In an attempt to work round the problem with readshortcut I reported
earlier, I thought I'd
Gerrit P. Haase wrote:
Wouldn't this problem be ameliorated slightly if the perl DLLs all
loaded in unique addresses to begin with? Isn't the problem that all
perl DLLs (and probably others) are loading in address 0x1000?
Gerrit, would you be willing to change this so that the DLLs load in
Christopher Faylor wrote:
On Thu, Jul 07, 2005 at 02:08:40PM -0400, Larry Hall wrote:
At 01:10 PM 7/7/2005, you wrote:
In an attempt to work round the problem with readshortcut I reported
earlier, I thought I'd use a Perl script. Unfortunately the
Win32::Shortcut package seems to cause probl
On Thu, Jul 07, 2005 at 02:08:40PM -0400, Larry Hall wrote:
>At 01:10 PM 7/7/2005, you wrote:
>>In an attempt to work round the problem with readshortcut I reported
>>earlier, I thought I'd use a Perl script. Unfortunately the
>>Win32::Shortcut package seems to cause problems with process forking
>
13 matches
Mail list logo
