Your message dated Mon, 18 Jun 2012 12:38:16 +0200
with message-id <4fdf0518.9000...@debian.org>
and subject line Re: Bug#671785: segfaults when running reportbug
has caused the Debian Bug report #671785,
regarding segfaults when running reportbug
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
671785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python2.7
Version: 2.7.3~rc2-2.1
Severity: grave
User: debian-...@lists.debian.org
Usertags: kfreebsd
$ LD_LIBRARY_PATH=/usr/lib/debug:/usr/lib/debug/lib/x86_64-kfreebsd-gnu gdb
--args python /usr/bin/reportbug
[...]
(gdb) r
Starting program: /usr/bin/python /usr/bin/reportbug
Please enter the name of the package in which you have found a problem, or type
'other' to report a more general problem.
>
Program received signal SIGSEGV, Segmentation fault.
__pthread_unlock (lock=0x13cd698) at spinlock.c:228
228 spinlock.c: El fitxer o directori no existeix.
(gdb) bt
#0 __pthread_unlock (lock=0x13cd698) at spinlock.c:228
#1 0x0000000800a85de9 in *__GI___pthread_mutex_unlock (mutex=<optimized out>)
at mutex.c:190
#2 0x00000008036d7c81 in g_mutex_unlock (mutex=<optimized out>)
at
/build/buildd-glib2.0_2.32.2-1-kfreebsd-amd64-QJQ4PI/glib2.0-2.32.2/./glib/gthread-posix.c:227
#3 0x00000008047a4a1f in IA__gtk_main () at
/build/buildd-gtk+2.0_2.24.10-1-kfreebsd-amd64-ErjCNI/gtk+2.0-2.24.10/gtk/gtkmain.c:1255
#4 0x0000000804359c24 in ?? () from
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so
#5 0x00000008027625d1 in readline_until_enter_or_signal (signal=<synthetic
pointer>, prompt=<optimized out>)
at
/home/rmh/hacking/kfreebsd/python/python2.7-2.7.3~rc2/Modules/readline.c:963
#6 call_readline (sys_stdin=<optimized out>, sys_stdout=<optimized out>,
prompt=<optimized out>)
at
/home/rmh/hacking/kfreebsd/python/python2.7-2.7.3~rc2/Modules/readline.c:1055
#7 0x000000000041faa2 in PyOS_Readline (sys_stdin=0x801ebea00,
sys_stdout=0x801ebeae0, prompt=0xf9b144 "> ") at ../Parser/myreadline.c:211
#8 0x00000000004c9595 in builtin_raw_input (self=<optimized out>,
args=<optimized out>) at ../Python/bltinmodule.c:2046
#9 0x00000000004d3d2d in call_function (oparg=<optimized out>,
pp_stack=0x7fffffffd2c0) at ../Python/ceval.c:4021
#10 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at
../Python/ceval.c:2666
#11 0x00000000004d58d6 in PyEval_EvalCodeEx (co=<optimized out>,
globals=<optimized out>, locals=<optimized out>, args=<optimized out>,
argcount=3, kws=
0x142dd88, kwcount=0, defs=0xf96888, defcount=3, closure=0x0) at
../Python/ceval.c:3253
[...]
Also reproducible with 2.7.2-11. As it appeared recently in sid it's probably
related to an upgrade of some other package.
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 8.1-1-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On 16.05.2012 08:29, Robert Millan wrote:
> 2012/5/13 Steven Chamberlain <ste...@pyro.eu.org>:
>> I couldn't reproduce this yet on either of two boxes:
>>
>> production server, up-to-date wheezy:
>> kfreebsd-amd64 9.0-1-amd64 9.0-3
>> python2.7 2.7.3~rc2-2.1
>> eglibc 2.13-32
>>
>> development VM, loosely following wheezy + some sid/experimental:
>> kfreebsd-i386 8.3-1-686 8.3-2
>> python2.7 2.7.3~rc2-2.1
>> eglibc 2.13-32+kkh901
>
> I hit it with up-to-date (at the time) sid chroot, hosted on kfreebsd 8.1.
>
> Is someone other than me able to reproduce this?
closing this now as not reproducible. Please feel free to reopen with a lower
severity, if you can reproduce it again on a different machine.
--- End Message ---
