From: Mikhail Usenko <cygwin@inbox.ru>
To: cygwin@cygwin.com
Subject: Re: info-6.1 segmentation fault
Date: Thu, 03 Mar 2016 20:01:00 -0000 [thread overview]
Message-ID: <20160303230057.dad325cdf38a34000b019dc4@inbox.ru> (raw)
In-Reply-To: <loom.20160303T164508-758@post.gmane.org>
On Thu, 3 Mar 2016 15:46:02 +0000 (UTC)
Achim Gratz <...> wrote:
> Mikhail Usenko <cygwin <at> inbox.ru> writes:
> > info 6.1 crashes to segmentation fault on every run.
> > Downgarding to version 6.0 resolves the problem.
> > Does anyone come across with this or it is my local issue?
>
> WJFFM. Local issue or some interaction with your environment is most
> likely. Have you run cygcheck?
>
Yes and it was/is OK for all installed packages.
I have just found the cause:
From strace output it can be observed that version 6.1
get an access violation exception after trying to read from the .infokey file.
And then, info-6.1 crashes if the .infokey file contains the lines that
disable the default key bindings by overriding them with the action 'invalid'
according to as described in info-stnd manual.
Perhaps it is an upstream bug.
--
Mike
--
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:[~2016-03-03 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 0:40 [ANNOUNCEMENT] Updated: texinfo-6.1-1 Ken Brown
2016-03-03 15:37 ` info-6.1 segmentation fault Mikhail Usenko
2016-03-03 15:46 ` Achim Gratz
2016-03-03 20:01 ` Mikhail Usenko [this message]
2016-03-03 20:31 ` Ken Brown
2016-03-04 21:12 ` Ken Brown
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=20160303230057.dad325cdf38a34000b019dc4@inbox.ru \
--to=cygwin@inbox.ru \
--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).