public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Ian Lambert <ian.lambert_42@yahoo.com>, cygwin <cygwin@cygwin.com>
Subject: Re: how to access and display apps that I've launched
Date: Wed, 26 Jul 2017 06:49:00 -0000	[thread overview]
Message-ID: <821a1b86-dd68-623d-3da1-72c9183c8d57@cornell.edu> (raw)
In-Reply-To: <799230527.525007.1500998733401@mail.yahoo.com>

On 7/25/2017 12:05 PM, Ian Lambert wrote:
> 
> --------------------------------------------
> On Tue, 7/25/17, Ken Brown <> wrote:
> 
>   Normally you don't ever
>   need to think about rebasing on x86_64.  The
>   perpetual postinstall script
>   /etc/postinstall/0p_000_autorebase.dash
>   should handle everything without any manual
>   intervention.  You might try
>   running that
>   script (and the rebaselst script that it calls) line by
>   line (preferably in a dash shell started
>   directly from Windows, with no
>   other Cygwin
>   processes running) to see if you can figure out what's
>    going wrong.
>   
> = = =
> Looks about the same to me, and all the /var/cache/rebase/...
> files are basically empty, FWIW, but I could be following
> the rebaselst script incorrectly.
> 
> 
> $ cat 0p_000_autorebase.dash
> #!/bin/dash
> export PATH=/bin
> b=/var/cache/rebase
> if [ -e ${b}/peflags ] ; then
>      noaslr=--noaslr
>      peflags=peflags
>      rm -f ${b}/peflags
> else
>      noaslr=''
>      peflags=''
> fi
> if [ ! -e ${b}/fullrebase.done ] ; then
>      rebase-trigger fullrebase
>      rebaselst --rebuild update --cleardb $noaslr rebase $peflags
>      mv ${b}/fullrebase ${b}/fullrebase.done
> else
>      rebaselst update $noaslr rebase $peflags
> fi
> 
> 
> 
> $ b=/var/cache/rebase
> $ ls ${b}/pe*
> ls: cannot access '/var/cache/rebase/pe*': No such file or directory
> $ ls ${b}/fullrebase.done
> /var/cache/rebase/fullrebase.done
> $ rebase-trigger fullrebase
> Note: _autorebase will do a full rebase the next time setup is run.
> $ rebaselst --rebuild update --cleardb rebase
> removing /var/cache/rebase/rebase_pkg
> creating empty /var/cache/rebase/rebase_pkg
> touch: setting times of '/var/cache/rebase/rebase_pkg': Invalid argument
> Updating package information in /var/cache/rebase/rebase_pkg.
> removing /var/cache/rebase/rebase_lst
> creating empty /var/cache/rebase/rebase_lst
> touch: setting times of '/var/cache/rebase/rebase_lst': Invalid argument
> Updating rebase information for installed executables in /var/cache/rebase/rebas
> e_exe.
> removing /var/cache/rebase/rebase_dyn
> creating empty /var/cache/rebase/rebase_dyn
> touch: setting times of '/var/cache/rebase/rebase_dyn': Invalid argument
> Looking for dynamic language modules/libraries in:
>    /usr/lib/R/site-library
>    /usr/lib/php/20151012
>    /usr/lib/python2.7/site-packages
>    /usr/lib/python3.6/site-packages
> Updating rebase information for dynamic language modules/libraries /var/cache/re
> base/rebase_dyn.
> removing /var/cache/rebase/rebase_user
> creating empty /var/cache/rebase/rebase_user
> touch: setting times of '/var/cache/rebase/rebase_user': Invalid argument
> Updating rebase information for user-defined dynamic objects /var/cache/rebase/r
> ebase_user.
> removing /var/cache/rebase/rebase_user_exe
> creating empty /var/cache/rebase/rebase_user_exe
> touch: setting times of '/var/cache/rebase/rebase_user_exe': Invalid argument
> Updating rebase information for user-defined executables /var/cache/rebase/rebas
> e_user_exe.
> Rebasing with list /var/cache/rebase/rebase_all, built from /var/cache/rebase/re
> base_lst /var/cache/rebase/rebase_dyn /var/cache/rebase/rebase_user.
> $
> 
> $ ls -ls /var/cache/rebase
> total 224
> 32 -rw-r--r-- 1 myuser Domain Users 115 Jul 25 10:50 fullrebase
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:34 rebase_all
> 32 -r--r--r-- 1 myuser Domain Users  31 Jul 25 11:34 rebase_dyn
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:33 rebase_dyn.old
> 32 -r--r--r-- 1 myuser Domain Users  31 Jul 25 11:33 rebase_exe
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:33 rebase_exe.old
> 32 -r--r--r-- 1 myuser Domain Users  31 Jul 25 11:33 rebase_lst
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:33 rebase_lst.old
> 32 -r--r--r-- 1 myuser Domain Users  31 Jul 25 11:33 rebase_pkg
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:33 rebase_pkg.old
> 32 -r--r--r-- 1 myuser Domain Users  31 Jul 25 11:34 rebase_user
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:34 rebase_user.old
> 32 -r--r--r-- 1 myuser Domain Users  31 Jul 25 11:34 rebase_user_exe
>   0 -rw-r--r-- 1 myuser Domain Users   0 Jul 25 11:34 rebase_user_exe.old

As Achim explained, the failure of 'touch' is causing rebaselst to think 
that no DLLs need to be rebased.  So that failure is the real problem to 
be solved.

This is a long shot, but I wonder if the touch failure is related to the 
bug reported in https://cygwin.com/ml/cygwin/2017-07/msg00114.html.  I 
think the bug is supposed to be fixed in the latest snapshot.  Can you 
try that snapshot and see if touch still fails?  If so, maybe you could 
run the touch command under strace to see if that sheds any light.

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

  parent reply	other threads:[~2017-07-25 19:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <799230527.525007.1500998733401.ref@mail.yahoo.com>
2017-07-25 18:21 ` Ian Lambert via cygwin
2017-07-25 21:52   ` Achim Gratz
2017-07-26  6:49   ` Ken Brown [this message]
     [not found] <1128827672.1514648.1501092281786.ref@mail.yahoo.com>
2017-07-27 16:01 ` Ian Lambert via cygwin
     [not found] <1534921570.1524318.1501093009415.ref@mail.yahoo.com>
2017-07-27 14:49 ` Ian Lambert via cygwin
     [not found] <685307372.1339085.1501078785472.ref@mail.yahoo.com>
2017-07-26 17:09 ` Ian Lambert via cygwin
2017-07-26 17:13   ` Ken Brown
2017-07-26 18:27     ` Brian Inglis
2017-07-27  2:38   ` Achim Gratz
     [not found] <1036849022.821922.1501019281615.ref@mail.yahoo.com>
2017-07-26  9:50 ` Ian Lambert via cygwin
2017-07-26 10:28   ` Brian Inglis
     [not found] <1438727230.474852.1500993486132.ref@mail.yahoo.com>
2017-07-25 18:12 ` Ian Lambert via cygwin
2017-07-25 18:16   ` Ken Brown
2017-07-25 19:57   ` Achim Gratz
     [not found] <1783227004.4348461.1500934105434.ref@mail.yahoo.com>
2017-07-24 22:49 ` Ian Lambert via cygwin
2017-07-25  0:03   ` mike
2017-07-25  4:27   ` Ken Brown
2017-07-25  4:55     ` Ian Lambert via cygwin
2017-07-25 15:06       ` Ken Brown
2017-07-25  5:21     ` Brian Inglis
2017-07-25 10:17       ` Brian Inglis
2017-07-25 11:57       ` Brian Inglis
2017-07-25 13:03       ` Brian Inglis
2017-07-25 14:13       ` Brian Inglis
2017-07-25 19:19       ` Achim Gratz
2017-07-26  8:16         ` Brian Inglis
2017-07-25 19:01     ` Achim Gratz
     [not found] <472748733.4076472.1500916852092.ref@mail.yahoo.com>
2017-07-24 19:46 ` Ian Lambert via cygwin
     [not found] <949225432.4024000.1500912514455.ref@mail.yahoo.com>
2017-07-24 18:07 ` Ian Lambert via cygwin
2017-07-24 20:22   ` Ken Brown
2017-07-23 14:25 mike
2017-07-23 17:39 ` Jack
2017-07-23 18:14   ` mike
2017-07-23 19:18     ` Brian Inglis
2017-07-23 19:46       ` mike
2017-07-24 17:31         ` Brian Inglis
2017-07-25  2:16           ` mike
2017-07-23 22:46 ` Ken Brown

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=821a1b86-dd68-623d-3da1-72c9183c8d57@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=ian.lambert_42@yahoo.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).