Closed Bug 450539 Opened 16 years ago Closed 16 years ago

JEMalloc should use different fill values

Categories

(Core :: Memory Allocator, defect)

Product:
Core
Component:
Memory Allocator
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: dbradley, Unassigned)

Details

Would be nice to have different fill values for uninitialized memory verses freed memory. This would allow quick diagnosis of what we're dealing with. The current use of the same values for both makes it difficult to figure out if we're looking at freed or uninitialized memory.
Right now, jemalloc fills uninitialized memory with 0xa5, and freed memory with 0x5a.  So, it does what you want already, right?
Status: NEW → ASSIGNED
Yes, you are correct, I glanced at it, and thought it was using the same value. Maybe that points to a nit about the values should be a little more distinguishable ;-)
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.