On Jun 7, 2012, at 18:04 , Justin C. Walker wrote: > > On Jun 7, 2012, at 17:52 , kcrisman wrote: >> >> On Thursday, June 7, 2012 8:21:01 PM UTC-4, Justin C. Walker wrote: >>> >>> On Jun 7, 2012, at 14:13 , Benjamin Jones wrote: >>> >>>> On Mac OS X 10.6.8 intel core i7 and sage-5.0 (also sage-5.1.beta2) I >>> can >>>> crash sage (and Maxima) by evaluating: >>>> >>>> sage: integrate(ln(1+4/5*sin(x)), x, -3.1415, 3.1415) >>> [snip] >>>> Has anyone seen similar crashes using sage-5.0 or earlier? >>> >>> I have duplicated this with Sage 5.0 on Mac OS X 10.6.8 (Dual 6-core >>> Xeons) and 10.7.4 (quad core Core i7). >>> >>> With 4.8 (10.6.8), sage just echos back what I typed in (no process is >>> spawned while this is being "processed"). >>> >>> The first version that gives the crash (rather than just echoing) seems to >>> be 5.0-b3 (b2 just echos). >>> >>> >> Hmm, strange, as one Maxima upgrade > >> was in b2 but the other > >> was in b8. > > I'm not sure that this is maxima: > - the only crash reports I see are for python > - I don't see maxima starting up when this is tested
> - I do see a python stack-athon > The latter is what seems to be behind the crash (the segfault is attributed > to python in the error message). FWIW, running "sage -gdb" (5.0-b3), I get this after the crash: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000008 0x000000010c91b867 in ecl_bds_unwind () (gdb) Is Maxima used as a library, or used with pexpect? I've lost track. Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds -- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. -- 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
