From: nilton.vasques@openmailbox.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:72423] [Ruby trunk - Bug #11857] [Open] Segmentation Fault in readline
Date: Mon, 21 Dec 2015 22:28:59 +0000 [thread overview]
Message-ID: <redmine.issue-11857.20151221222858.637e4caeb0b09c94@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11857.20151221222858@ruby-lang.org
Issue #11857 has been reported by Nilton Vasques.
----------------------------------------
Bug #11857: Segmentation Fault in readline
https://bugs.ruby-lang.org/issues/11857
* Author: Nilton Vasques
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: 2.2.3
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
I'm using a rails environment and this bug happens after I put rspec gem in my Gemfile and run a bundle install.
The log generated after segmentation is attachment and I'm available for further clarifications about the bug.
The bug nows persistent occur when I run rake, rails c or rails s.
---Files--------------------------------
error.log (246 KB)
--
https://bugs.ruby-lang.org/
parent reply other threads:[~2015-12-21 21:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <redmine.issue-11857.20151221222858@ruby-lang.org>]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-11857.20151221222858.637e4caeb0b09c94@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/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).