On Oct 7, 11:44 am, "Dr. David Kirkby" <david.kir...@onetel.net> 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 relatively new, as I do *NOT* see the segfault at > > http://t2nb.math.washington.edu:8000 > > which is running Sage 4.5.1. That said, that's a big-endian machine, which > could > just be relevant.
Conceivable, since it's definitely not new, as I get ---------------------------------------------------------------------- | Sage Version 4.4.4, Release Date: 2010-06-23 | | Type notebook() for the GUI, and license() for information. | ---------------------------------------------------------------------- Loading Sage library. Current Mercurial branch is: hackbranch sage: copy(x) ------------------------------------------------------------ Unhandled SIGSEGV: A segmentation fault occurred in Sage. This probably occurred because a *compiled* component of Sage has a bug in it (typically accessing invalid memory) or 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 (sorry). ------------------------------------------------------------ While on my PPC OS X 10.4 machine, I just get a long hang (this is 4.6.alpha2) with no output. So at any rate the behavior is very machine-dependent at this point, but not really ideal on any of them (with the possible exception of t2). - kcrisman -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
