From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com, Rainer.Woitok@gmail.com
Subject: Re: How to correctly rebase?
Date: Fri, 16 Oct 2015 12:58:00 -0000 [thread overview]
Message-ID: <5620F460.7020605@cornell.edu> (raw)
In-Reply-To: <22048.47638.206600.117271@woitok.gmail.com>
On 10/16/2015 4:49 AM, Dr Rainer Woitok wrote:
> Ken,
>
> On Thursday, 2015-10-15 17:10:38 -0400, you wrote:
>
>> ...
>> Another possibility is that those DLLs were in use. Rainer, did you make sure
>> that no Cygwin processes were running other than dash?
>
> Well, at least I tried to. I ran "/bin/ps -ef" and only saw one "ps"
> and one "ash" process.
>
>> ...
>> No, it's because rebase is called with the -s option, which implies the -d
>> option, which means that it starts at 0x70000000 and works down.
>
> Thanks for the explanation. This had escaped me.
>
>> Rainer, you
>> can run 'rebase -is' to see the full list of base addresses.
>
> I did, and I think this list os more or less the same as the output from
> "rebaslst". But I'll compare more thoroughly later. What caught my eye
> though is that both lists seemed sorted more or less with respect to de-
> scending file names, except for
>
> /usr/bin/cygLLVM-3.1.dll base 0x5ca90000 size 0x0128a000
> /home/Rainer/repo/netcdf/bin/cygnetcdf-7.dll base 0x5dd20000 size 0x032a0000
> /usr/bin/cygORBitCosNaming-2-0.dll base 0x61580000 size 0x0000c000
>
> All my other local DLLs appear at the very end of these lists. Is this
> just the way "rebase" works internally or does this indicate a problem?
I don't know off the top of my head, but I wouldn't worry about this.
>
> Talking about problems: Python still does not work (and perhaps other
> stuff I just haven't yet tried). Should I try re-installing Python?
>
> But I would be more at rest if this all would be sort of explainable.
As Warren and Achim have both suggested, you may just have too many DLLs for
32-bit Cygwin. Can you uninstall some unneeded packages? Or switch to 64-bit
Cygwin?
By the way, I don't think you have yet attached cygcheck output as requested in
http://cygwin.com/problems.html: "Run cygcheck -s -v -r > cygcheck.out and
include that file as an attachment in your report. Please do not compress or
otherwise encode the output. Just attach it as a straight text file so that it
can be easily viewed." Maybe someone will spot something.
Ken
--
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:[~2015-10-16 12:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:26 Dr Rainer Woitok
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27 ` Achim Gratz
2015-10-14 21:30 ` Warren Young
2015-10-14 22:08 ` Warren Young
2015-10-14 22:37 ` Warren Young
2015-10-15 7:53 ` Achim Gratz
2015-10-15 7:15 ` Achim Gratz
2015-10-15 13:16 ` Dr Rainer Woitok
2015-10-15 20:54 ` Warren Young
2015-10-15 21:10 ` Ken Brown
2015-10-16 12:57 ` Dr Rainer Woitok
2015-10-16 12:58 ` Ken Brown [this message]
2015-10-16 15:08 ` Ken Brown
2015-10-16 15:16 ` cyg Simple
2015-10-16 15:29 ` Ken Brown
2015-10-16 15:50 ` Andrey Repin
2015-10-18 11:15 ` Dr Rainer Woitok
2015-10-18 11:59 ` Achim Gratz
2015-10-18 12:45 ` Ken Brown
2015-10-18 16:20 ` Dr Rainer Woitok
2015-10-19 23:59 ` Warren Young
2015-10-20 16:55 ` Dr Rainer Woitok
2015-10-16 7:21 ` Achim Gratz
2015-10-16 20:11 ` Warren Young
2015-12-18 16:28 ` Achim Gratz
2015-10-14 19:58 ` 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=5620F460.7020605@cornell.edu \
--to=kbrown@cornell.edu \
--cc=Rainer.Woitok@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).