| 1 |
Hi, |
| 2 |
|
| 3 |
On Tuesday 26 October 2010 22:14:12 v_2e@×××.net wrote: |
| 4 |
> On Wed, 27 Oct 2010 08:45:00 +1300 |
| 5 |
> |
| 6 |
> François Bissey <f.r.bissey@×××××××××.nz> wrote: |
| 7 |
> > I believe you may be the first person to try out python 2.6.6 with sage. |
| 8 |
> > You may need to rebuild cython-0.12.1 (don't use 0.13) possibly numpy, |
| 9 |
> > scipy, pexpect, ipython, matplotlib, mpmath, sympy, pynac, networx, |
| 10 |
> > sphinx and then rebuild sage-clib and sage itself again. There may be |
| 11 |
> > more but any one of these could be at fault. |
| 12 |
> |
| 13 |
> I have rebuilt Cython-0.12.1 today just before starting this thread. |
| 14 |
> So, this is not because of Cython, I guess. I'll try to rebuild the |
| 15 |
> packages you mentioned one by one and find the one causing the |
| 16 |
> segfault. And then report back here. |
| 17 |
|
| 18 |
If you do not find anything, please try the following: |
| 19 |
|
| 20 |
USE=debug emerge -1 sage-baselayout |
| 21 |
|
| 22 |
Also, make sure that the GNU Debugger is installed (emerge gdb). You may now |
| 23 |
start Sage with |
| 24 |
|
| 25 |
sage -gdb |
| 26 |
|
| 27 |
which spawns Sage in a gdb session. Sage will crash just as before, but you |
| 28 |
may retrieve a backtrace via typing |
| 29 |
|
| 30 |
bt |
| 31 |
|
| 32 |
That output would be interesting and may directly lead us to the root of the |
| 33 |
problem. |
| 34 |
|
| 35 |
> |
| 36 |
> Regards, |
| 37 |
> Vladimir |
| 38 |
> |
| 39 |
> ----- |
| 40 |
> <v_2e@×××.net> |
| 41 |
|
| 42 |
Cheers, |
| 43 |
|
| 44 |
Christopher |
Archives