On Sep 15, 4:07 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> On Sep 15, 2008, at 3:56 PM, Simon King wrote:
>
>
>
> > Dear Robert,
>
> > On Sep 16, 12:46 am, Robert Bradshaw <[EMAIL PROTECTED]>
> > wrote:
> >> Try running as sage -gdb , which will catch the error. Then you can
> >> type "bt" at the prompt to get a c traceback.
>
> > I don't understand what the following tells me.
> > When there should be an error raised, instead i get:
>
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 46922761735376 (LWP 26484)]
> > 0x000000000041befe in instancemethod_call (func=0x34ba680,
> > arg=0x36ebab8,
> >     kw=0x0) at Objects/classobject.c:2477
> > 2477    Objects/classobject.c: Datei oder Verzeichnis nicht gefunden.
> >         in Objects/classobject.c
> > (gdb) bt
> > #0  0x000000000041befe in instancemethod_call (func=0x34ba680,
> > arg=0x36ebab8,
> >     kw=0x0) at Objects/classobject.c:2477
> > #1  0x0000000000415913 in PyObject_Call (func=0x36ebab8,
> > arg=0x36ebab8, kw=0x0)
> >     at Objects/abstract.c:1861
> > #2  0x000000000047efd2 in PyEval_CallObjectWithKeywords
> > (func=0x35a4f00,
> >     arg=0x36ebab8, kw=0x0) at Python/ceval.c:3442
> > #3  0x000000000041dd68 in instance_getattr (inst=<value optimized
> > out>,
> >     name=0x99a840) at Objects/classobject.c:755
> > #4  0x00002aad32fd7298 in ?? ()
> > #5  0x0000000000000000 in ?? ()
>
> > That's all. But what does it mean?
>
> Hmm... that's not a very informative traceback (just generic Python  
> calls). I would try putting some print statements in. What is the  
> return type of the function you're raising an error from?
>
> - Robert

There are a couple things you can do:

a) boil it down to a simple patch against some recent 3.1.x and I can
take a look.
b) Build the Sage library with "-O0". To do so edit $SAGE_ROOT/local/
lib/python2.5/config/Makefile and change

# Compiler options
OPT=            -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes

to

# Compiler options
OPT=            -DNDEBUG -g -fwrapv -O0 -Wall -Wstrict-prototypes

Maybe that will help. Then do a "sage -ba" to rebuild the whole Sage
library

If that still does not help you can also build Python with "-O0", but
we can do that later.

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to