2009/11/18 Aivo Jürgenson <aivo.jurgen...@gmail.com>:
>
> From: Aivo Jürgenson <aivo.jurgen...@gmail.com>
> Date: November 18, 2009 10:20:05 PM GMT+02:00
> To: sage-devel@googlegroups.com
> Subject: sage 4.2.1 on 64bit mac 10.6.2 and the plot function crashes
>
> Hello.
>
> I'm running the sage 4.2.1 on a 64 bit macosx 10.6.2 and I'm not able to use 
> plot(sin(x),0,4) style functions. It seems that this is related to the 
> http://trac.sagemath.org/sage_trac/ticket/7022 issue, which should be fixed, 
> but unfortunately doesn't work in my machine.
>
> The sage console shows:

What happens when you type

sage: plot(sin(x),0,4)

on the command line?

This command definitely works fine for me with 64 bit macosx 10.6.2.

William

>
> 2009-11-18 21:53:43+0200 [HTTPChannel,1,127.0.0.1] got EOF subprocess must 
> have crashed...
>
> and the ~/Library/Logs/DiagnosticReports/python_2009-11-18-214233_mind.crash 
> logs are created with the following backtrace:
>
> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
> 0   libSystem.B.dylib                   0x00007fff867f4fe6 __kill + 10
> 1   libSystem.B.dylib                   0x00007fff86895dd3 __abort + 103
> 2   libSystem.B.dylib                   0x00007fff86895e41 abort_report_np + 0
> 3   libgcc_s.1.dylib                    0x0000000103e89d51 uw_init_context_1 
> + 385
> 4   libgcc_s.1.dylib                    0x0000000103e8a4cc _Unwind_Resume + 76
> 5   ft2font.so                          0x000000010b39c49d 
> FT2Font::FT2Font(std::string) + 4269
> 6   ft2font.so                          0x000000010b39cb28 
> ft2font_module::new_ft2font(Py::Tuple const&) + 408
> 7   ft2font.so                          0x000000010b39fd82 
> Py::ExtensionModule<ft2font_module>::invoke_method_varargs(std::string 
> const&, Py::Tuple const&)
> + 162
> 8   ft2font.so                          0x000000010b3ae5d0 
> method_varargs_call_handler + 512
> 9   python                              0x00000001000b3b25 PyEval_EvalFrameEx 
> + 23061
> 10  python                              0x00000001000b4ce0 PyEval_EvalCodeEx 
> + 2112
> 11  python                              0x00000001000b2afd PyEval_EvalFrameEx 
> + 18925
> 12  python                              0x00000001000b4ce0 PyEval_EvalCodeEx 
> + 2112
> 13  python                              0x0000000100034fb5 function_call + 165
> ...
>
> Could it be my fault or is it a bug in sage components?
>
> Aivo Jürgenson, aivo.jurgen...@gmail.com
>
>
>
>
> --
> 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
Associate 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