What version of XCode, GCC, etc.?  Did you upgrade anything?  This
looks like exactly the sort of bug that one would have with XCode 4.x
but *not* with XCode 3.x.

On Thu, Mar 29, 2012 at 8:15 AM, Starx <jst...@gmail.com> wrote:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
> 0x0000000107b9e5f4 in PyInt_FromLong (ival=-5) at Objects/intobject.c:91
> 91      Objects/intobject.c: No such file or directory.
>        in Objects/intobject.c
> (gdb) bt
> #0  0x0000000107b9e5f4 in PyInt_FromLong (ival=-5) at Objects/intobject.c:91
> #1  0x0000000107b143ba in GiNaC::Number_T::Number_T ()
> #2  0x0000000107b14440 in GiNaC::numeric::numeric ()
> #3  0x0000000107b6557a in GiNaC::library_init::library_init ()
> #4  0x00000001079edc98 in __static_initialization_and_destruction_0 ()
> #5  0x00007fff5fc0d500 in
> __dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkContextE
> ()
> #6  0x00007fff5fc0bcec in
> __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEj
> ()
> #7  0x00007fff5fc0bc9d in
> __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEj
> ()
> #8  0x00007fff5fc0bda6 in
> __dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextE ()
> #9  0x00007fff5fc08fbb in __dyld_dlopen ()
> #10 0x00007fff82b6be40 in dlopen ()
> #11 0x00000001000e88bf in _PyImport_GetDynLoadFunc ()
> #12 0x00000001000d2e14 in _PyImport_LoadDynamicModule ()
> #13 0x00000001000d10ef in import_submodule ()
> #14 0x00000001000d160a in load_next ()
> #15 0x00000001000d1962 in PyImport_ImportModuleLevel ()
> #16 0x00000001000aef23 in builtin___import__ ()
> #17 0x000000010000bd02 in PyObject_Call ()
> #18 0x00000001000b0177 in PyEval_CallObjectWithKeywords ()
> #19 0x00000001000b443e in PyEval_EvalFrameEx ()
> #20 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #21 0x00000001000b9126 in PyEval_EvalCode ()
> #22 0x00000001000cdfe0 in PyImport_ExecCodeModuleEx ()
> #23 0x00000001000cf242 in load_source_module ()
> #24 0x00000001000d10ef in import_submodule ()
> #25 0x00000001000d160a in load_next ()
> #26 0x00000001000d1962 in PyImport_ImportModuleLevel ()
> #27 0x00000001000aef23 in builtin___import__ ()
> #28 0x000000010000bd02 in PyObject_Call ()
> #29 0x00000001000b0177 in PyEval_CallObjectWithKeywords ()
> #30 0x00000001000b443e in PyEval_EvalFrameEx ()
> #31 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #32 0x00000001000b9126 in PyEval_EvalCode ()
> #33 0x00000001000cdfe0 in PyImport_ExecCodeModuleEx ()
> #34 0x00000001000cf242 in load_source_module ()
> #35 0x00000001000d10ef in import_submodule ()
> #36 0x00000001000d160a in load_next ()
> #37 0x00000001000d1962 in PyImport_ImportModuleLevel ()
> #38 0x00000001000aef23 in builtin___import__ ()
> #39 0x000000010000bd02 in PyObject_Call ()
> #40 0x00000001000b0177 in PyEval_CallObjectWithKeywords ()
> #41 0x00000001000b443e in PyEval_EvalFrameEx ()
> #42 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #43 0x00000001000b9126 in PyEval_EvalCode ()
> #44 0x00000001000cdfe0 in PyImport_ExecCodeModuleEx ()
> #45 0x00000001000cf242 in load_source_module ()
> #46 0x00000001000d10ef in import_submodule ()
> #47 0x00000001000d160a in load_next ()
> #48 0x00000001000d191c in PyImport_ImportModuleLevel ()
> #49 0x00000001000aef23 in builtin___import__ ()
> #50 0x00000001000b82e8 in PyEval_EvalFrameEx ()
> #51 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #52 0x00000001000b702d in PyEval_EvalFrameEx ()
> #53 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #54 0x00000001000b702d in PyEval_EvalFrameEx ()
> #55 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #56 0x000000010003b0dd in function_call ()
> #57 0x000000010000bd02 in PyObject_Call ()
> #58 0x000000010001dd3d in instancemethod_call ()
> #59 0x000000010000bd02 in PyObject_Call ()
> #60 0x00000001000b0177 in PyEval_CallObjectWithKeywords ()
> #61 0x0000000100020d3e in PyInstance_New ()
> #62 0x000000010000bd02 in PyObject_Call ()
> #63 0x00000001000b45ae in PyEval_EvalFrameEx ()
> #64 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #65 0x00000001000b702d in PyEval_EvalFrameEx ()
> #66 0x00000001000b9040 in PyEval_EvalCodeEx ()
> #67 0x00000001000b9126 in PyEval_EvalCode ()
> #68 0x00000001000dde3e in PyRun_FileExFlags ()
> #69 0x00000001000de0f9 in PyRun_SimpleFileExFlags ()
> #70 0x00000001000eb61b in Py_Main ()
> #71 0x0000000100000f14 in start ()
>
> -Jim
>
> On Wed, Mar 28, 2012 at 11:42 PM, William Stein <wst...@gmail.com> wrote:
>> What does "./sage -gdb", then running sage, then typing "bt" when it crashes
>> show?
>>
>> On Thu, Mar 29, 2012 at 7:12 AM, Starx <jst...@gmail.com> wrote:
>>>
>>> So I planned to build a new copy of 4.8 and then try out -upgrade to
>>> get beta11... but I couldn't build 4.8!!  I got the following after
>>> the build:
>>>
>>> Testing that Sage starts...
>>> [2012-03-28 22:52:38] Sage version 4.8, released 2012-01-20
>>>
>>> ------------------------------------------------------------------------
>>> Unhandled SIGSEGV: A segmentation fault occurred in Sage.
>>> This probably occurred because a *compiled* component of Sage has a bug
>>> in it and is not properly wrapped with sig_on(), sig_off(). You might
>>> want to run Sage under gdb with 'sage -gdb' to debug this.
>>> Sage will now terminate.
>>> ------------------------------------------------------------------------
>>> local/bin/sage-sage: line 766: 20815 Segmentation fault      sage-eval
>>> "$@"
>>> Sage failed to start up.
>>> Please email sage-devel (http://groups.google.com/group/sage-devel)
>>> explaining the problem and send the log file
>>>  /Users/Starx/sage-dev/start.log
>>> Describe your computer, operating system, etc.
>>> make: *** [start] Error 1
>>>
>>> The log file it mentions has the same message.  I'm running OSX 10.6.8
>>> on a MacBook Pro.  I've built sage before so I don't know why it wont
>>> work now.
>>>
>>> -Jim
>>>
>>> --
>>> Die Dunkelheit... leitet die Musik.
>>> Die Musik... leitet die Seele.
>>>
>>> --
>>> To post to this group, send an email to sage-devel@googlegroups.com
>>> To unsubscribe from this group, send an email to
>>> sage-devel+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/sage-devel
>>> URL: http://www.sagemath.org
>>
>>
>>
>>
>> --
>> William Stein
>> Professor of Mathematics
>> University of Washington
>> http://wstein.org
>>
>> --
>> To post to this group, send an email to sage-devel@googlegroups.com
>> To unsubscribe from this group, send an email to
>> sage-devel+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/sage-devel
>> URL: http://www.sagemath.org
>
>
>
> --
> Die Dunkelheit... leitet die Musik.
> Die Musik... leitet die Seele.
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to 
> sage-devel+unsubscr...@googlegroups.com
> For more options, visit this group at 
> http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org



-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to