From: ir. Tjeerd Pinkert <t.j.pinkert@vu.nl>
To: buildroot@busybox.net
Subject: [Buildroot] ipython segfaults on history when no SQLite available
Date: Tue, 24 Mar 2015 14:54:46 +0100 [thread overview]
Message-ID: <55116CA6.5050806@vu.nl> (raw)
In-Reply-To: <5509AA8E.6000409@vu.nl>
This appears to be a bug in readline, see:
https://github.com/ipython/ipython/issues/8087#issuecomment-83660592
On 18-03-15 17:40, ir. Tjeerd Pinkert wrote:
> I notice that ipython segfaults on the following conditions:
> - no SQLite
> - a command is not found in the history list when arrow-up is pressed.
>
> The following snapshots apply:
> ------------------------------
> # ipython
> WARNING: IPython History requires SQLite, your history will not be saved
> Python 2.7.9 (default, Mar 17 2015, 11:45:11)
>
>
>
> It crashes in this case nothing with "rela" is found in the history:
> --------------------------------------------------------------------
> In [17]: relapython[1380]: unhandled signal 11 at 00000000 nip b6b10940
> lr b6b10934 code 30001
> Segmentation fault
> #
>
>
> System is MPC8313E, powerpc
> This might be an upstream issue.
>
> Best regards,
>
>
> Tjeerd
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2015-03-24 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 16:17 [Buildroot] [PATCH 1/1] GNURadio: add processing blocks Gwenhael Goavec-Merou
2015-03-18 16:40 ` [Buildroot] ipython segfaults on history when no SQLite available ir. Tjeerd Pinkert
2015-03-24 13:54 ` ir. Tjeerd Pinkert [this message]
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=55116CA6.5050806@vu.nl \
--to=t.j.pinkert@vu.nl \
--cc=buildroot@busybox.net \
/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