On Sun, 22 Jan 2012 16:58:54 Stephen Montgomery-Smith wrote:
> On 01/22/2012 04:28 PM, Stephen Montgomery-Smith wrote:
> > On 01/22/2012 04:24 PM, François Bissey wrote:
> >> On Sun, 22 Jan 2012 15:54:19 Stephen Montgomery-Smith wrote:
> >>> On 01/21/2012 08:23 PM, Stephen Montgomery-Smith wrote:
> >>>> On 01/21/2012 08:05 PM, Stephen Montgomery-Smith wrote:
> >>>>> I am able to build sage on FreeBSD. I have attached a tar file
> >>>>> which
> >>>>> contains a "port" to build sage on FreeBSD. (FreeBSD users will
> >>>>> know
> >>>>> what I mean by a "port.")
> >>>>> 
> >>>>> It does seem to work, but it segfaults on exit:
> >>>>> 
> >>>>> %./sage
> >>>>> ----------------------------------------------------------------
> >>>>> ------>>>>> 
> >>>>> | Sage Version 4.8, Release Date: 2012-01-20 |
> >>>>> | Type notebook() for the GUI, and license() for information.
> >>>>> | |
> >>>>> 
> >>>>> ----------------------------------------------------------------
> >>>>> ------ sage: 1+1
> >>>>> 2
> >>>>> sage: exit
> >>>>> Exiting Sage (CPU time 0m0.03s, Wall time 0m6.24s).
> >>>>> local/bin/sage-sage: line 303: 22511 Segmentation fault: 11
> >>>>> (core
> >>>>> dumped) sage-ipython "$@" -i
> >>>>> 
> >>>>> Any ideas on how to proceed?
> >>>> 
> >>>> I did a "sage -gdb" and it suggests that the problem might be to
> >>>> do
> >>>> with
> >>>> ~Commentator in commentator.C. This is part of the linbox
> >>>> subpackage. I did a google and found this:
> >>>> http://trac.sagemath.org/sage_trac/ticket/11718
> >>>> 
> >>>> Does construction and/or deconstruction of Commentator tend to
> >>>> cause
> >>>> problems?
> >>> 
> >>> I fixed the problem as follows:
> >>> 
> >>> sed -i .bak -e 's/Commentator/Commensator/g' \
> >>> "$SAGE_ROOT"/local/lib/liblinboxsage.so.0
> >>> 
> >>> That way sage didn't get confused between the Commentator that
> >>> appears
> >>> in liblinbox and liblinboxsage.
> >>> 
> >>> Now I am getting a different segmentation fault, for which
> >>> unfortunately gdb provides no clues.
> >> 
> >> Can you still post what output/debugging info you have?
> > 
> > I am in the process of compiling with the "-g" option set. I'll send you
> > the output when this is done.
> 
> The "-g" option didn't seem to help one bit.  This is what I got.
> 
> Not all of the subpackages respect CFLAGS or CXXFLAGS.  But I don't know
> if that is the reason the symbols are not showing up.
> 
> Any advice?
> 

export SAGE_DEBUG=yes
then build.

> %./sage -gdb
> ----------------------------------------------------------------------
> 
> | Sage Version 4.8, Release Date: 2012-01-20                         |
> | Type notebook() for the GUI, and license() for information.        |
> 
> ----------------------------------------------------------------------
> /usr/home/stephen/sage/work/sage-4.8/local/bin/sage-ipython
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...
> [New LWP 100403]
> [New Thread 8012041c0 (LWP 100403/initial thread)]
> Python 2.6.4 (r264:75706, Jan 22 2012, 22:20:43)
> [GCC 4.6.3 20120113 (prerelease)] on freebsd8
> Type "help", "copyright", "credits" or "license" for more information.
> sage:
> Exiting Sage (CPU time 0m0.02s, Wall time 0m2.62s).
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 8012041c0 (LWP 100403/initial thread)]
> 0x0000000000000000 in ?? ()
> (gdb) backtrace
> #0  0x0000000000000000 in ?? ()
> #1  0x0000000800f1b086 in __cxa_finalize () from /lib/libc.so.7
> #2  0x0000000800ec5787 in exit () from /lib/libc.so.7

That little bit makes me suspect an issue similar to:
https://github.com/cschwan/sage-on-gentoo/issues/40
also found on solaris at some point:
http://trac.sagemath.org/sage_trac/ticket/11116

Francois

-- 
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