How to correctly rebase?

Ken Brown kbrown@cornell.edu
Fri Oct 16 12:58:00 GMT 2015


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



More information about the Cygwin mailing list