ipython crashed with SIGSEGV in _rl_dispatch_callback()

[Adam Collard]

Was exploring base64 module, tried to decode "foo" a few times with different variations, when I came back to the terminal (note it was running in byobu) I saw the segfault

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: ipython 1.2.1-2
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 10 11:26:49 2014
ExecutablePath: /usr/bin/ipython
InstallationDate: Installed on 2012-08-17 (569 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ipython
SegvAnalysis:
 Segfault happened at: 0x7f3188b42209 <_rl_dispatch_callback+9>: testb $0x1,(%rdi)
 PC (0x7f3188b42209) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ipython
StacktraceTop:
 _rl_dispatch_callback () from /lib/x86_64-linux-gnu/libreadline.so.6
 rl_callback_read_char () from /lib/x86_64-linux-gnu/libreadline.so.6
 ?? () from /usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so
 PyOS_Readline ()
 ?? ()
Title: ipython crashed with SIGSEGV in _rl_dispatch_callback()
UpgradeStatus: Upgraded to trusty on 2014-02-08 (29 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 _rl_dispatch_callback (cxt=0x0) at /build/buildd/readline6-6.3/readline.c:728
 rl_callback_read_char () at /build/buildd/readline6-6.3/callback.c:188
 readline_until_enter_or_signal (signal=<synthetic pointer>, prompt=<optimized out>) at /build/buildd/python2.7-2.7.6/Modules/readline.c:1000
 call_readline (sys_stdin=<optimized out>, sys_stdout=<optimized out>, prompt=<optimized out>) at /build/buildd/python2.7-2.7.6/Modules/readline.c:1088
 PyOS_Readline (sys_stdin=0x7f318ca9e640 <_IO_2_1_stdin_>, sys_stdout=sys_stdout@entry=0x7f318ca9e400 <_IO_2_1_stdout_>, prompt=prompt@entry=0x7f3189c64284 "\n\001\033[0;34m\002In [\001\033[1;34m\002\063\001\033[0;34m\002]: \001\033[0m\002") at ../Parser/myreadline.c:207

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Julian Taylor (jtaylor)]

its a readline issue

patch available here
http://lists.gnu.org/archive/html/bug-readline/2014-03/msg00031.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741555

[Julian Taylor (jtaylor)]

this is the correct upstream patch, its the same as in debianb: http://lists.gnu.org/archive/html/bug-readline/2014-03/msg00034.html

[Launchpad Janitor (janitor)]

This bug was fixed in the package readline6 - 6.3-1ubuntu2

---------------
readline6 (6.3-1ubuntu2) trusty; urgency=medium

  * rl_dispatch_callback-segv.diff: Add upstream patch from Chet Ramey
    SIGSEGV in _rl_dispatch_callback() (Closes: #741555, LP: #1290287)
 -- Adam Conrad <email address hidden> Fri, 14 Mar 2014 14:37:56 -0600