X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:content-type :content-transfer-encoding:date:from:to:subject:in-reply-to :references:message-id; q=dns; s=default; b=ow9PHm5ALkCOvxcGNYuz ArcZX+5sy6Uceh4aegqtJQ4lDXAQ9QfNlvPoqv+kR7xKPAGInY8RidM0ZxTYhZ0E imkoIMZHESuw0BDt7LOzNAzf5gJtSIYGTQ1ItfrqvhfpcAL1Ase+ZQYxyObJgULD zSch2LBmTUuVjyUZd0Ocfac= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:content-type :content-transfer-encoding:date:from:to:subject:in-reply-to :references:message-id; s=default; bh=43tkYn4OciYKQUtJDToVOzD8i8 k=; b=WoTFvah8gbbtyi40zF5pnCuMmR17KlfkycHasEMWkpi4ZU4OScV4J/J4ud Ke9dbbj/sw2DE/FhkYvV0JwNZ3e/GdOUTsBP21RSxrN6FsRFavNjqDaaa69/nxKI 0PoOQoYLTcvTPlivg0eokGGEJSLMuWxAP2vhWouesFFjFJxJ0= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=H*UA:1.3.8, H*u:1.3.8, proposition, deserves X-HELO: www16.qth.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 15 Aug 2019 12:22:40 -0400 From: Chris Wagner To: cygwin AT cygwin DOT com Subject: Re: Perl Illegal Instruction In-Reply-To: <87zhleee0j.fsf@Rainer.invalid> References: <1a666ba9c75538fb2d246545a6e06343 AT plebeian DOT com> <87ims3nkrw DOT fsf AT Rainer DOT invalid> <802fce1aec7fcce7b453fafc36b0b310 AT plebeian DOT com> <87zhleee0j DOT fsf AT Rainer DOT invalid> Message-ID: <5bf2dbe26a4630ae03d229f869c3f4b8@plebeian.com> X-Sender: wagnerc AT plebeian DOT com User-Agent: Roundcube Webmail/1.3.8 X-IsSubscribed: yes Apologies for the necropost but the solution deserves to be documented. I suspected that it could be a rebasing issue and sure enough having Setup do a rebase fixed the problem. Rebasing should probably be the first thing to do whenever you get some weird execution error from a Cygwin program. Thanks. On 2019-07-16 1:37 am, Achim Gratz wrote: > Chris Wagner writes: >> Of course it's up to date... > > I'll let that stand, although I've seen sufficiently many Win7 systems > lately to be wary of any such statement. > >> That is not BLODA. That's the standard list of libraries. I changed >> nothing; it worked yesterday; today it didn't. Every other Cygwin >> executable I've tried works without problem. I even tried >> reextracting the files from perl_base. > > So again, something changed and you have no idea what. If you rule out > a hardware error (memory most likely if it always strikes at the same > place) and you didn't actively made changes (not limited to Cygwin), > then the culprit must by definition be some change that occured > elsewhere in the system. If it was some automatic update there might > be a restore point pertaining to those changes and certainly something > in the event logs. > >>>> $ uname -a >>>> CYGWIN_NT-6.1 applejack 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 >>>> Cygwin >>> >>> A current Cygwin... >>> >>>> $ cygcheck -c perl perl_base >>>> Cygwin Package Information >>>> Package Version Status >>>> perl 5.22.4-1 OK >>>> perl_base 5.22.4-1 OK >>> >>> combined with an outdated Perl (Cygwin is at 5.26.3 now). What are >>> you >>> trying to achieve? Please fully update Cygwin after checking your >>> system. Also, you might want to clean up your PATH a bit. >> >> I'm not going to recompile all my modules and rework the new lib paths >> until I have a really good reason to. > > As they say, "you break it, you get to keep the broken pieces". Trying > to lock down part(s) of Cygwin is a losing proposition unless you are > building everything yourself, at which point building a bunch of Perl > modules after an update ceases to be an issue anyway. > >> I'ld be happy to run any other diagnostic command anyone can think of. > > Well, as I said, try to start with some halfway sane PATH perhaps? In > other words, something like > > env PATH=/bin perl --version > > for starters. > > > Regards, > Achim. -- 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