From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Perl Illegal Instruction
Date: Mon, 15 Jul 2019 19:46:00 -0000 [thread overview]
Message-ID: <87ims3nkrw.fsf@Rainer.invalid> (raw)
In-Reply-To: <1a666ba9c75538fb2d246545a6e06343@plebeian.com> (Chris Wagner's message of "Mon, 15 Jul 2019 13:56:56 -0400")
Chris Wagner writes:
> For some reason this afternoon, after having worked fine, my Perl
> stopped working. There was no error message. It just silently died
> with status 0 no less.
>
> Windows 7 SP1.
Terribly out of date and no longer safe to use on a networked system.
> So I turn to strace and it states Illegal Instruction. Any ideas?
BLODA or worse, assuming that _you_ didn't change anything recently.
> $ 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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
--
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
next prev parent reply other threads:[~2019-07-15 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 17:57 Chris Wagner
2019-07-15 18:50 ` Andrey Repin
2019-07-15 19:46 ` Achim Gratz [this message]
2019-07-15 19:58 ` Achim Gratz
2019-07-15 20:36 ` Chris Wagner
2019-07-15 21:01 ` Vince Rice
2019-07-16 5:37 ` Achim Gratz
2019-08-15 16:22 ` Chris Wagner
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=87ims3nkrw.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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).