This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Mar 27 14:32, Ken Brown wrote:On 3/27/2012 2:20 PM, Corinna Vinschen wrote:On Mar 27 14:01, Ken Brown wrote:I just tried it, and the list of DLLs that couldn't be rebased does indeed appear in setup.log.full. I also get a warning from setup.exe about the exit code of autorebase.bat, which some users might interpret as meaning that autorebase.bat failed. I wonder if you'd be better off suppressing this warning somehow.
That's unexpected. The fact that rebase prints the warnings doesn't mean it returns with a non-0 exit code. In fact, as far as I can see, the only reason to fail with a non-0 exit code after printing the "The following DLLs couldn't be rebased" messages would be if saving the database failed, which also means you should see a message "failed to create temporary rebase database" or "failed to write rebase database" in the log. If such a message is not printed, I don't understand where the non-0 exit code is coming from.
There's no such message, and /etc/rebase.db.i386 does have the same timestamp as I find at the end of setup.log. Here are the last few lines of setup.log:
2012/03/27 13:48:01 Extracting from file://C:\downloads\cygwin/http%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f/release/python/python-crypto/python-crypto-2.5-1.tar.bz2 2012/03/27 13:48:01 Changing gid back to original 2012/03/27 13:48:01 running: cmd.exe /c C:\cygwin\etc\postinstall\autorebase.bat 2012/03/27 13:48:07 abnormal exit: exit code=-1073741819 2012/03/27 13:48:07 Changing gid to Administrators 2012/03/27 13:48:19 note: Installation Complete 2012/03/27 13:48:19 Ending cygwin install
And the last part of setup.log.full is:
2012/03/27 13:48:01 running: cmd.exe /c C:\cygwin\etc\postinstall\autorebase.bat
The following DLLs couldn't be rebased because they were in use: /usr/lib/gio/modules/cygdconfsettings.dll [...] /usr/bin/cygICE-6.dll 2012/03/27 13:48:07 abnormal exit: exit code=-1073741819
Hmm. The batch file is very simple:
@echo off rem Postinstall scripts are always started from the Cygwin root dir rem so we can just call dash from here path .\bin;%path% dash -c "/bin/rebaseall -p"
That's all. -1073741819 is the decimal notation of the status code 0xC0000005, STATUS_ACCESS_VIOLATION. Where on earth is that coming from? Do you have a dash.exe.stackdump file in / by any chance?
Attachment:
cygcheck.out
Description: Text document
-- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |