I've been reading an old post Sage + Eclipse + PyDev
http://groups.google.com/group/sage-support/browse_thread/thread/ac94be0a91863467/07b0f8c43223321b?lnk=gst&q=eclipse#07b0f8c43223321b
Many moons later, I have the same problem. Some things change, some
stay the same. It still doesn't work runnin
On Thu, Oct 7, 2010 at 6:25 PM, kcrisman wrote:
> LOL - I should have checked that! Trac isn't working now - can you or
> drkirkby put that on the ticket when it comes back up?
I've already posted a patch.
--Mike
--
To post to this group, send email to sage-support@googlegroups.com
To unsubsc
On Oct 7, 8:50 pm, Mike Hansen wrote:
> It doesn't have anything to do with the compiler warning messages --
> the problem is much simpler than that. The implementation of
> Element.__copy__ is wrong for Expression objects; namely, it doesn't
> set the _gobj attribute. To fix it, we just add a
It doesn't have anything to do with the compiler warning messages --
the problem is much simpler than that. The implementation of
Element.__copy__ is wrong for Expression objects; namely, it doesn't
set the _gobj attribute. To fix it, we just add a proper
implementation of copy:
def __copy__
On 10/ 7/10 09:05 PM, kcrisman wrote:
While on my PPC OS X 10.4 machine, I just get a long hang (this is
4.6.alpha2) with no output.
More precisely, with sage -gdb I get
sage: copy(x)
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at addre
On Oct 7, 5:02 pm, "Dr. David Kirkby" wrote:
> On 10/ 7/10 08:55 PM, kcrisman wrote:
>
>
>
>
>
>
>
> > On Oct 7, 11:44 am, "Dr. David Kirkby"
> > wrote:
> >> On 10/ 6/10 03:18 PM, Jean-Pierre Flori wrote:
>
> >>> Sage segfaults when printing a copy of something symbolics :
>
> >>> sage: copy(x)
On 10/ 7/10 08:55 PM, kcrisman wrote:
On Oct 7, 11:44 am, "Dr. David Kirkby"
wrote:
On 10/ 6/10 03:18 PM, Jean-Pierre Flori wrote:
Sage segfaults when printing a copy of something symbolics :
sage: copy(x)
As I noted earlier, I see this on my machine (Sun Ultra 27 running OpenSolaris).
I tried to save a Sage notebook I made on one of the public Sage
servers and noticed some content at the end was chopped off and some
cells in the middle were gone.
I think I saw this a few months ago. Is there a fix for this?
Perhaps the public Sage servers have old versions? Or maybe this is a
> While on my PPC OS X 10.4 machine, I just get a long hang (this is
> 4.6.alpha2) with no output.
>
More precisely, with sage -gdb I get
sage: copy(x)
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x
GiNaC::ex::print (this
On Oct 7, 11:44 am, "Dr. David Kirkby"
wrote:
> On 10/ 6/10 03:18 PM, Jean-Pierre Flori wrote:
>
> > Sage segfaults when printing a copy of something symbolics :
>
> > sage: copy(x)
>
> As I noted earlier, I see this on my machine (Sun Ultra 27 running
> OpenSolaris).
> However, it must be rela
On 10/ 6/10 03:18 PM, Jean-Pierre Flori wrote:
Sage segfaults when printing a copy of something symbolics :
sage: copy(x)
As I noted earlier, I see this on my machine (Sun Ultra 27 running OpenSolaris).
However, it must be relatively new, as I do *NOT* see the segfault at
http://t2nb.math.w
On 7 oct, 01:36, Jason Grout wrote:
> On 10/6/10 9:18 AM, Jean-Pierre Flori wrote:
>
>
>
> > Sage segfaults when printing a copy of something symbolics :
>
> > sage: copy(x)
>
> >
> > Unhandled SIGSEGV: A segmentation fault occurred in
12 matches
Mail list logo
