| 1 |
I doubt this is a memory problem. I've just had the same problem with |
| 2 |
glibc-2.17 and python. I manually went back to glibc-2.16 and everything is |
| 3 |
fine again. I then tried re-emerging all the python versions with glibc-2.16 |
| 4 |
installed and then re-emerged glibc-2.17 and had the same problem. |
| 5 |
|
| 6 |
After running strace on the python2.7. My best guess is that it is a kernel |
| 7 |
<> glibc-2.17 incompatiblity. The segfault happens near a mprotect |
| 8 |
operation, very early on. |
| 9 |
|
| 10 |
vault ~ # strace python |
| 11 |
-- snip -- |
| 12 |
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = |
| 13 |
0xb7462000 |
| 14 |
set_thread_area({entry_number:-1 -> 6, base_addr:0xb74626c0, limit:1048575, |
| 15 |
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, |
| 16 |
seg_not_present:0, useable:1}) = 0 |
| 17 |
mprotect(0xb7658000, 8192, PROT_READ) = 0 |
| 18 |
--- SIGSEGV (Segmentation fault) @ 0 (0) --- |
| 19 |
+++ killed by SIGSEGV +++ |
| 20 |
Segmentation fault |
| 21 |
|
| 22 |
vault ~ # uname -a |
| 23 |
Linux vault 2.6.31-gentoo-r10 #1 SMP Sun Mar 7 14:35:15 EST 2010 i686 |
| 24 |
Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz GenuineIntel GNU/Linux |
| 25 |
|
| 26 |
I'm upgrading to the latest gentoo-sources. Only thing i'm worried about is |
| 27 |
rebooting but all in the life of a gentoo user. |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
View this message in context: http://gentoo.2317880.n4.nabble.com/updating-old-box-segfaults-with-python-tp274112p274799.html |
| 33 |
Sent from the gentoo-user mailing list archive at Nabble.com. |
Archives