Re: [sage-support] kernel keeps dying

2018-11-02 Thread slelievre
Please can you say how this was solved for you? Le lundi 29 octobre 2018 16:21:01 UTC+1, mali claramunt: > > already solved, thank you > > El lun., 29 oct. 2018 a las 15:59, Dima Pasechnik: > >> On Mon, Oct 29, 2018 at 2:23 PM mali claramunt: >> > >> > I don't know how to >> >> use the usual gmail

Re: [sage-support] kernel keeps dying

2018-10-29 Thread mali claramunt
already solved, thank you El lun., 29 oct. 2018 a las 15:59, Dima Pasechnik () escribió: > On Mon, Oct 29, 2018 at 2:23 PM mali claramunt > wrote: > > > > I don't know how to > > use the usual gmail interface to send email to > >sage-support@googlegroups.com > > including this file as an att

Re: [sage-support] kernel keeps dying

2018-10-29 Thread Dima Pasechnik
On Mon, Oct 29, 2018 at 2:23 PM mali claramunt wrote: > > I don't know how to use the usual gmail interface to send email to sage-support@googlegroups.com including this file as an attachment. > > > El 29 oct 2018, a les 14:23, Dima Pasechnik va escriure: > > Could you please post here t

Re: [sage-support] kernel keeps dying

2018-10-29 Thread mali claramunt
I don't know how to > El 29 oct 2018, a les 14:23, Dima Pasechnik va escriure: > > Could you please post here this file, mentioned in your message: > > /var/folders/52/xrnm3lb510ldyrqvrvgp__jmgn/T/tmpYMG6Nj/Sage_crash_report.txt > > On 29 Oct 2018 1:32 pm, "mali claramunt"

Re: [sage-support] kernel keeps dying

2018-10-29 Thread Dima Pasechnik
Could you please post here this file, mentioned in your message: /var/folders/52/xrnm3lb510ldyrqvrvgp__jmgn/T/tmpYMG6Nj/Sage_ crash_report.txt On 29 Oct 2018 1:32 pm, "mali claramunt" wrote: > macos 10.13.6 , sagemath doesn't work, kernel on sage keeps dying. > > Oops, Sage crashed. We do o

[sage-support] kernel keeps dying

2018-10-29 Thread mali claramunt
macos 10.13.6 , sagemath doesn't work, kernel on sage keeps dying. Oops, Sage crashed. We do our best to make it stable, but... A crash report was automatically generated with the following information: - A verbatim copy of the crash traceback. - A copy of your input history during this se