not sure if that is python per se... if I rebuild python-rpy on my somewhat outdated laptop (runs squeeze with sid but no regular full-installation upgrades) -- everything works fine... (rebuilding in uptodate sid chroot leads to failing one again).
I am still on elderly libc:
$> apt-cache policy libgfortran3 gcc-4.4-base libgcc1
libgfortran3:
Installed: 4.4.1-1
Candidate: 4.4.1-1
Version table:
4.4.1-3 0
600 http://debian.lcs.mit.edu sid/main Packages
*** 4.4.1-1 0
900 http://debian.lcs.mit.edu squeeze/main Packages
100 /var/lib/dpkg/status
gcc-4.4-base:
Installed: 4.4.1-1
Candidate: 4.4.1-1
Version table:
4.4.1-3 0
600 http://debian.lcs.mit.edu sid/main Packages
*** 4.4.1-1 0
900 http://debian.lcs.mit.edu squeeze/main Packages
100 /var/lib/dpkg/status
libgcc1:
Installed: 1:4.4.1-1
Candidate: 1:4.4.1-1
Version table:
1:4.4.1-3 0
600 http://debian.lcs.mit.edu sid/main Packages
*** 1:4.4.1-1 0
900 http://debian.lcs.mit.edu squeeze/main Packages
100 /var/lib/dpkg/status
FWIW he is a traceback of segfault:
$> LD_LIBRARY_PATH=/usr/lib/debug gdb /usr/bin/python
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) set args -c "import rpy"
(gdb) r
Starting program: /usr/bin/python -c "import rpy"
[Thread debugging using libthread_db enabled]
[New Thread 0x7f73b23ee6f0 (LWP 28773)]
[New Thread 0x7f73aac5f950 (LWP 28796)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f73b23ee6f0 (LWP 28773)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007f73acfd1906 in ?? () from
/usr/lib/python2.5/site-packages/_rpy2092.so
#2 0x00000000004911d5 in PyEval_EvalFrameEx (f=0x2fe3ef0, throwflag=<value
optimized out>) at ../Python/ceval.c:3612
#3 0x00000000004924cd in PyEval_EvalCodeEx (co=0x7f73b23a33f0, globals=<value
optimized out>, locals=<value optimized out>, args=0x24b19e8, argcount=1,
kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0)
at ../Python/ceval.c:2875
#4 0x00000000004dc992 in function_call (func=0x24afed8, arg=0x24b19d0, kw=0x0)
at ../Objects/funcobject.c:517
#5 0x0000000000418843 in PyObject_Call (func=0x7f73b23ce300,
arg=0x7f73b2327e68, kw=0x7f73b0f3bea0) at ../Objects/abstract.c:1861
#6 0x000000000041f6e8 in instancemethod_call (func=0x24afed8, arg=0x24b19d0,
kw=0x0) at ../Objects/classobject.c:2519
#7 0x0000000000418843 in PyObject_Call (func=0x7f73b23ce300,
arg=0x7f73b2327e68, kw=0x7f73b0f3bea0) at ../Objects/abstract.c:1861
#8 0x000000000048b322 in PyEval_CallObjectWithKeywords (func=0x7f73b2310640,
arg=0x7f73b23ae050, kw=0x0) at ../Python/ceval.c:3481
#9 0x0000000000422496 in PyInstance_New (klass=<value optimized out>,
arg=0x7f73b23ae050, kw=0x0) at ../Objects/classobject.c:560
#10 0x0000000000418843 in PyObject_Call (func=0x7f73b23ce300,
arg=0x7f73b2327e68, kw=0x7f73b0f3bea0) at ../Objects/abstract.c:1861
#11 0x000000000048e061 in PyEval_EvalFrameEx (f=0x2247950, throwflag=<value
optimized out>) at ../Python/ceval.c:3823
#12 0x00000000004924cd in PyEval_EvalCodeEx (co=0x7f73b23a38a0, globals=<value
optimized out>, locals=<value optimized out>, args=0x0, argcount=0, kws=0x0,
kwcount=0, defs=0x0, defcount=0, closure=0x0)
at ../Python/ceval.c:2875
#13 0x00000000004926c2 in PyEval_EvalCode (co=0x7f73b23ce300,
globals=0x7f73b2327e68, locals=0x7f73b0f3bea0) at ../Python/ceval.c:514
#14 0x00000000004a725e in PyImport_ExecCodeModuleEx (name=0x7fff1277ee30 "rpy",
co=0x7f73b23a38a0, pathname=0x7fff1277cd00
"/usr/lib/python2.5/site-packages/rpy.pyc") at ../Python/import.c:675
#15 0x00000000004a7508 in load_source_module (name=0x7fff1277ee30 "rpy",
pathname=0x7fff1277cd00 "/usr/lib/python2.5/site-packages/rpy.pyc", fp=<value
optimized out>) at ../Python/import.c:959
#16 0x00000000004a8ac4 in import_submodule (mod=0x72ecc0,
subname=0x7fff1277ee30 "rpy", fullname=0x7fff1277ee30 "rpy") at
../Python/import.c:2400
#17 0x00000000004a8d5c in load_next (mod=0x72ecc0, altmod=0x72ecc0,
p_name=<value optimized out>, buf=0x7fff1277ee30 "rpy",
p_buflen=0x7fff1277fe38) at ../Python/import.c:2220
#18 0x00000000004a93bd in import_module_level (name=0x0, globals=0x224a300,
locals=<value optimized out>, fromlist=0x72ecc0, level=-1) at
../Python/import.c:2001
#19 0x00000000004a976f in PyImport_ImportModuleLevel (name=0x7f73b23a9414
"rpy", globals=0x224a300, locals=0x224a300, fromlist=0x72ecc0, level=-1) at
../Python/import.c:2072
#20 0x000000000048ae39 in builtin___import__ (self=<value optimized out>,
args=<value optimized out>, kwds=<value optimized out>) at
../Python/bltinmodule.c:47
#21 0x0000000000418843 in PyObject_Call (func=0x7f73b23ce300,
arg=0x7f73b2327e68, kw=0x7f73b0f3bea0) at ../Objects/abstract.c:1861
#22 0x000000000048b322 in PyEval_CallObjectWithKeywords (func=0x7f73b23bb5f0,
arg=0x7f73b23819f0, kw=0x0) at ../Python/ceval.c:3481
#23 0x000000000048db56 in PyEval_EvalFrameEx (f=0x22944b0, throwflag=<value
optimized out>) at ../Python/ceval.c:2093
#24 0x00000000004924cd in PyEval_EvalCodeEx (co=0x7f73b2397198, globals=<value
optimized out>, locals=<value optimized out>, args=0x0, argcount=0, kws=0x0,
kwcount=0, defs=0x0, defcount=0, closure=0x0)
at ../Python/ceval.c:2875
#25 0x00000000004926c2 in PyEval_EvalCode (co=0x7f73b23ce300,
globals=0x7f73b2327e68, locals=0x7f73b0f3bea0) at ../Python/ceval.c:514
#26 0x00000000004b342c in PyRun_SimpleStringFlags (command=<value optimized
out>, flags=0x7fff12780320) at ../Python/pythonrun.c:1273
#27 0x0000000000413f53 in Py_Main (argc=1, argv=<value optimized out>) at
../Modules/main.c:521
#28 0x00007f73b16275c6 in __libc_start_main () from /lib/libc.so.6
#29 0x00000000004139b9 in _start ()
On Tue, 01 Sep 2009, Dirk Eddelbuettel wrote:
> (CC to doko added re Python, see below)
> On 1 September 2009 at 18:19, Michael Rutter wrote:
> | Dirk,
> | Is that 64bit as well?
> Yup. I only run amd64 Ubuntu at work. Thanks for rebuilding python-rpy so
> quickly!
> This may be a toolchain issue. I should contact doko -- ccing Doko.
> Matthias: All of a sudden the 'rpy' R module for Python segfauls on Debian
> (see original bug report #544564) whereas the courtesy backport we do via the
> R "CRAN" network works on my Ubuntu Jaunty amd64 works. Did something
> change at Debian's Python end?
> Dirk
> | Michael
> | Dirk Eddelbuettel wrote:
> | > PS: And on Ubuntu it also works with Python 2.5. Hm.
> | > Dirk
> | --
> | Dr. Michael A. Rutter
> | School of Science
> | Penn State Erie, The Behrend College
> | Station Road
> | Erie, PA 16563
> | http://math.bd.psu.edu/faculty/rutter
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
signature.asc
Description: Digital signature
