X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8C125385E02E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1707917485; bh=eAFP7EPR28GwKGt5mCFFmBZPcWCWFuXSzjJY1yiCNEM=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=mGdiYlqrHOAoGqG6LDe40H5Pt5+yyVse3PbfYvOEzkeEnJI3vel8TggkvP5x4lWU8 U6uqvdarxurldqYSPD252wOV8OA62XeIlKQQgaSM7xd9lymOOTqytsORBegfEJxDXd evX05bR7YDHU3DOo3EQC9IPftsRXCkRtapXepiwY= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DB081385DC30 Date: Wed, 14 Feb 2024 14:30:32 +0100 To: cygwin AT cygwin DOT com Subject: Re: Cygwin installer hangs when running post-install scripts Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com, Kevin Ushey References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen , Kevin Ushey Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Feb 14 10:52, Corinna Vinschen via Cygwin wrote: > On Feb 13 15:48, Kevin Ushey via Cygwin wrote: > > Here's a bit more information from a debug build of cygwin; here I'm > > just trying to launch cygpath.exe: > > > > (gdb) f 1 > > #1 0x00007ffa0123ba1f in find_fast_cwd_pointer () at > > ../../../../winsup/cygwin/path.cc:4526 > > 4526 const uint8_t *lock = (const uint8_t *) > > > > (gdb) bt > > #0 memmem (haystack=, hs_len=, > > needle=0x7ffa0142e531 <_C_collate_locale+59857>, ne_len=4) at > > ../../../newlib/libc/string/memmem.c:161 > > #1 0x00007ffa0123ba1f in find_fast_cwd_pointer () at > > ../../../../winsup/cygwin/path.cc:4526 > > [...] > > Ok, so we know now which memmem call fails, so the next question is, > why? The haystack address is unfortunately still optimized out in > memmem, so it looks like the newlib subdir is still optimized. > But it's pretty certainly a wrong haystack address. This address has > been fetched from > > const uint8_t *rcall = (const uint8_t *) memchr (get_dir, 0xe8, 80); > ... > const uint8_t *use_cwd = rcall + 5 + peek32 (rcall + 1); > > Chances are high, that the call instruction found by rcall is bogus. Can you run this in GDB? I'd love to see the assembler code starting at address `get_dir'... Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple