#5862: [with patch, needs work] OSX 64 bit libsingular -- sage/libsingular
segfaults on first creation of a ring
---------------------------------+------------------------------------------
Reporter: was | Owner: malb
Type: defect | Status: new
Priority: major | Milestone: sage-4.0
Component: commutative algebra | Keywords:
---------------------------------+------------------------------------------
Comment(by malb):
Here's what I believe is the cause of the problem:
When oMalloc creates a new bucket it assigns the global {{{om_ZeroPage}}}
to {{{s_bin->bin->current_page}}} in {{{omBin.c}}}, a NULL pointer so to
speak.
It is defined in {{{om_Alloc.c}}} as {{{omBinPage_t om_ZeroPage[] = {{0,
NULL, NULL, NULL, NULL}};}}}. In {{{omInsertBinPage}}} it checks whether
the current page is this zero page and this is where things go wrong. It
should detect that it indeed deals with the zero page and take another
code path. However, for some reason there are at least two
{{{om_ZeroPage}}} objects around, i.e. the pointer comparison fails.
Linker fun ahead!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5862#comment:7>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
