From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault
Date: Tue, 26 Oct 2010 11:45:31 +0200 [thread overview]
Message-ID: <201010261145.32136.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <20101026123223.d0b84170.v_2e@ukr.net>
Hi!
On Tuesday 26 October 2010 11:32:23 v_2e@ukr.net wrote:
> Hello!
> After a recent software update on my amd64-based machine, I get the
> following message trying to launch Sage:
>
> ------------------------------------------------------------
> 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).
> ------------------------------------------------------------
>
> And then it just exits. I have no idea where to search for the reasons
> of such behaviour, so decided to ask here. :)
I need a bit more of information - do you use the latest stable (4.5.3) or the
release candiate version ? Is there any additional text printed which gives a
hint ?
>
> Thanks.
> Vladimir
>
> -----
> <v_2e@ukr.net>
Cheers,
Christopher
prev parent reply other threads:[~2010-10-26 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 9:32 [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault v_2e
2010-10-26 9:38 ` François Bissey
2010-10-26 18:53 ` v_2e
2010-10-26 19:45 ` François Bissey
2010-10-26 20:14 ` v_2e
2010-10-27 8:07 ` Christopher Schwan
2010-10-27 21:34 ` v_2e
2010-10-27 22:08 ` François Bissey
2010-11-10 23:00 ` v_2e
2010-11-11 8:51 ` Christopher Schwan
2010-11-26 11:32 ` Jari_42
2010-11-29 10:43 ` Christopher Schwan
2010-12-01 10:14 ` v_2e
2010-12-01 10:29 ` Christopher Schwan
2010-10-26 9:45 ` Christopher Schwan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010261145.32136.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox