From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Does Cygwin setup modify dlls?
Date: Fri, 22 Sep 2017 14:46:00 -0000 [thread overview]
Message-ID: <16302f48-6e7c-7af2-6a2e-15091794769a@gmail.com> (raw)
In-Reply-To: <0ec4a5bf-d608-68d2-973d-3e8b5db33589@cs.umass.edu>
On 22/09/2017 16:11, Eliot Moss wrote:
> On 9/22/2017 10:00 AM, Joachim Eibl wrote:
>> Hi,
>> In our project we like the Cygwin-Setup tool so much that we use it
>> for our own files too.
>> Adding our archives to our setup.ini was easy enough and almost
>> everything worked as expected.
>> But then a certain tool didn't work and we found that dll-files that
>> were unpacked by the Cygwin-installer didn't match the files in the
>> archive.
>> The problem seems to be dll-specific. Other filetypes are not modified.
>
> Cygwin's rebasing of DLLs does modify the files (slightly).
> Others can probably detail the exact nature of what changes,
> and perhaps the comparison tool can be refined to ignore that
> as a difference.
the change is on ImageBase address
$ objdump -x /usr/bin/cygglpk-40.dll |grep ImageBase
ImageBase 00000003e1710000
$ rebase -si |grep /usr/bin/cygglpk-40.dll
/usr/bin/cygglpk-40.dll
base 0x0003e1710000 size 0x000ec000
To perform a proper fork all the dlls should be loaded
at not colliding address
This activity is performed by the script
/etc/postinstall/0p_000_autorebase.dash
after the files installation.
> Regards - Eliot Moss
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-09-22 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 14:00 Joachim Eibl
2017-09-22 14:11 ` Eliot Moss
2017-09-22 14:46 ` Marco Atzeri [this message]
[not found] ` <trinity-4204847c-6bba-4606-b43c-8b376b96a945-1506094235587@3c-app-gmx-bs22>
2017-09-22 15:31 ` Joachim Eibl
2017-09-22 16:49 ` Marco Atzeri
2017-09-27 4:50 ` Andrey Repin
2017-09-27 10:04 ` Joachim Eibl
2017-09-22 15:49 ` Eliot Moss
2017-09-23 19:53 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16302f48-6e7c-7af2-6a2e-15091794769a@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).