[issue8154] os.execlp('true') crashes the interpreter on 2.x

Matthias Klose report at bugs.python.org
Wed Mar 17 01:40:05 CET 2010


Matthias Klose <doko at debian.org> added the comment:

crash seen on both Debian unstable and recent Ubuntu lucid.

(gdb) run
Starting program: /home/doko/a.out 
process 30155 is executing new program: /bin/ls
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
strrchr () at ../sysdeps/i386/strrchr.S:178
178	../sysdeps/i386/strrchr.S: No such file or directory.
	in ../sysdeps/i386/strrchr.S
(gdb) bt
#0  strrchr () at ../sysdeps/i386/strrchr.S:178
#1  0x080524d2 in ?? ()
#2  0x0804fb2c in ?? ()
#3  0x00170bd6 in __libc_start_main (main=0x804fb10, argc=0, 
    ubp_av=0xbffff534, init=0x805bd60, fini=0x805bd50, 
    rtld_fini=0x11e0b0 <_dl_fini>, stack_end=0xbffff52c) at libc-start.c:226
#4  0x08049cf1 in ?? ()

stack trace from lucid; glibc-2.11.1, linux 2.6.32

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8154>
_______________________________________


More information about the Python-bugs-list mailing list