#5344: [with patch, needs work] Singular/omalloc "double free" problem
-------------------------+--------------------------------------------------
 Reporter:  GeorgSWeber  |       Owner:  mabshoff  
     Type:  defect       |      Status:  new       
 Priority:  critical     |   Milestone:  sage-3.4.1
Component:  packages     |    Keywords:            
-------------------------+--------------------------------------------------

Comment(by GeorgSWeber):

 OK, I try tp rephrase it:

 There is a hidden Singular related bug "four double frees". Currently it
 occurs only for OS X 64Bit and is brought to light by using "--with-
 malloc=system", as in the patch attached to #4181. It is also possible to
 make it appear by switching to "--with-malloc=external" and then using the
 original dlmalloc, as explained above in the original description.

 But:


 The patch attached to this ticket does *not* touch the build of omalloc
 (or the underlying mem allocator) at all! (There is no "--with-malloc
 whatsoever" in it).


 Instead, the patch to this ticket attempts to fix an issue in the Singular
 kernel. From both reading the code and from my tests it is obvious that
 the Singular kernel at a certain place screws up its memory management
 (see the end of the description above), mixing two different "free()"
 implementations.

 And I'm unsure what exactly you mean by "switching back and forth from/to
 mmap" --- could please be more verbose on that?

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5344#comment:5>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to