[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    Re: [Haiku-bugs] [Haiku] #4164: assertion fails in malloc (rev
From:       "Blub" <trac () haiku-os ! org>
Date:       2009-07-31 21:23:37
Message-ID: 048.55df70b4606ceba7d1bdde12bf89c920 () haiku-os ! org
[Download RAW message or body]

#4164: assertion fails in malloc (rev 31961)
-------------------------------+--------------------------------------------
 Reporter:  Blub               |       Owner:  axeld         
     Type:  bug                |      Status:  new           
 Priority:  normal             |   Milestone:  R1            
Component:  System/libroot.so  |     Version:  R1 development
Blockedby:                     |    Platform:  All           
 Blocking:                     |  
-------------------------------+--------------------------------------------

Comment(by Blub):

 seems like it was a double-free corruption, but I cannot really confirm
 that since I couldn't find the place where it actually happened.

 I have a testcase where I was able to successfully double-free some data
 without any errors or assertion faults coming up, so I guess the errors
 occur some time too late.

 After changing the data-layout of the program it didn't crash anymore
 (actually it is now optimized better since it doesn't fragment the memory
 as much)

 I guess I'm just too used to glibc's huge and frightening "double free
 corruption" error message.

 However, when I double-freed on purpose in my testcase (sometimes it did
 actually cause a crash) then it has always been a different assertion.
 (and it's always been the same different assertions)

 Maybe if I have time to read through the malloc code I can add a check for
 double-free corruptions (if until then it's not already made).

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/4164#comment:1>
Haiku <http://dev.haiku-os.org>
The Haiku operating system.
_______________________________________________
Haiku-bugs mailing list
Haiku-bugs@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/haiku-bugs
[prev in list] [next in list] [prev in thread] [next in thread]