From: Rainer Emrich <rainer-lists@emrich-ebersheim.de>
To: Jon Turney <jon.turney@dronecode.org.uk>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.911)
Date: Thu, 30 Dec 2021 20:04:32 +0100 [thread overview]
Message-ID: <3b727033-4493-42e7-fece-13227c68471b@emrich-ebersheim.de> (raw)
In-Reply-To: <5609cdcd-7bd8-cc16-fb6a-c1ae5ec5d19e@emrich-ebersheim.de>
Some additional Info.
Am 30.12.2021 um 19:31 schrieb Rainer Emrich:
> Hi Jon,
>
> thanks for your quick answer.
>
> Am 30.12.2021 um 18:38 schrieb Jon Turney:
>> On 30/12/2021 16:45, Rainer Emrich wrote:
>>> Hi Jon,
>>>
>>> Am 29.12.2021 um 16:58 schrieb Jon Turney:
>>>> A new version of Setup (2.911) has been uploaded to:
>>>>
>>>> https://cygwin.com/setup-x86_64.exe (64 bit version)
>>>> https://cygwin.com/setup-x86.exe (32 bit version)
>>>>
>>> for me the new setup executables do not work, same for both:
>>>
>>> Microsoft Windows [Version 10.0.19044.1415]
>>> (c) Microsoft Corporation. Alle Rechte vorbehalten.
>>>
>>> D:\System\Software\cygwin-all>setup-x86_64.exe --version
>>>
>>> D:\System\Software\cygwin-all>Cygwin setup 2.911
>>>
>>> D:\System\Software\cygwin-all>setup-x86_64.exe
>>>
>>> D:\System\Software\cygwin-all>Starting cygwin install, version 2.911
>>> User has backup/restore rights
>>> User has symlink creation right
>>
>> That's disappointing.
>>
>> Perhaps you can try the following (unfortunately complex) procedure to
>> help me investigate the problem:
>>
>> 1. Using an old setup from https://cygwin.com/setup/, install the gdb
>> and upx packages.
>>
>> 2. Fetch setup 2.911, and the corresponding symbols. Make sure setup
>> is executable.
>>
>> $ wget https://cygwin.com/setup/setup-2.911.x86_64.exe
>> $ chmod +x setup-2.911.x86_64.exe
>> $ wget https://cygwin.com/setup/setup-2.911.x86_64.dbg
>>
>> 3. Decompress the setup executable using 'upx -d'.
>>
>> $ upx -d setup-2.911.x86_64.exe
>>
>> 4. Run setup under gdb. Avoid elevation so setup stays under the
>> control of gdb. Load the symbol file into gdb.
>>
>> $ gdb --args ./setup-2.911.x86_64.exe -B
>> [...]
>> (gdb) symbol-file setup-2.911.x86_64.dbg
>> Reading symbols from setup-2.911.x86_64.dbg...
>> (gdb) r
>>
>> 5. When gdb reports an error, capture a backtrace.
>>
>> (gdb) bt full
> I get the following:
>
> (gdb) r
> Starting program: /home/rainer/tmp/setup-2.911.x86_64.exe -B
> [New Thread 23512.0x4d2c]
> [New Thread 23512.0x4e2c]
> [New Thread 23512.0x585c]
> Starting cygwin install, version 2.911
> User has NO backup/restore rights
> User has symlink creation right
> [Thread 23512.0x4d2c exited with code 1]
> [Thread 23512.0x4e2c exited with code 1]
> [Thread 23512.0x585c exited with code 1]
>
> Program terminated with signal SIGHUP, Hangup.
> The program no longer exists.
> (gdb)
>
> That's for a unprivileged user.
>
My unpriveleged user has symlink creation right and the SYSTEM CYGWIN
environment variable is set to winsymlink:native.
next prev parent reply other threads:[~2021-12-30 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 15:58 Jon Turney
2021-12-30 16:45 ` Rainer Emrich
2021-12-30 17:38 ` Jon Turney
2021-12-30 18:31 ` Rainer Emrich
2021-12-30 19:04 ` Rainer Emrich [this message]
2021-12-30 18:38 ` Doug Henderson
2021-12-31 14:38 ` Jon Turney
2021-12-31 15:02 ` Rainer Emrich
2022-01-01 14:15 ` © Fxzx mic
2022-01-01 15:14 ` Marco Atzeri
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=3b727033-4493-42e7-fece-13227c68471b@emrich-ebersheim.de \
--to=rainer-lists@emrich-ebersheim.de \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).