>> 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.
I have Xcode 3.2.6, but 'which gcc' no longer returns anything. I did
have gcc and have no idea where it could have gone. Fr
On Thursday, March 29, 2012 12:48:20 AM UTC-7, William wrote:
>
> 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.
Along the same lines as William's questions, you could try bui
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 wrote:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALI
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x
0x000107b9e5f4 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 0
What does "./sage -gdb", then running sage, then typing "bt" when it
crashes show?
On Thu, Mar 29, 2012 at 7:12 AM, Starx 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 t
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
-
