Skip to contentSkip to conversation

New: malloc(3) should document MALLOC_PERTURB_ env option

Bug 20102 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 3 messages Oct 11, 2010 – Oct 23, 2010 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=20102

Summary: malloc(3) should document MALLOC_PERTURB_ env option
Product: Documentation
Version: unspecified
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
AssignedTo: documentation_man-pages-ztI5WcYan/[email protected]
ReportedBy: [email protected]
Regression: No

setting MALLOC_PERTURB_ in the env will take that number and initialize all malloc's with that value (and the inverse when freeing). this should be documented in malloc(3) (and noted in free(3)).

e.g. if you set MALLOC_PERTURB_=123, glibc will do memset((123 ^ 0xff) & 0xff) when doing malloc(), and then glibc will do memset(123 & 0xff) when doing free()

Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw

[Bug 20102] malloc(3) should document MALLOC_PERTURB_ env option

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=20102

Michael Kerrisk <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |ASSIGNED
                 CC|                            |[email protected]

--- Comment #1 from Michael Kerrisk <[email protected]> 2010-10-23 12:31:55 --- Mike,

Thanks for the heads-up on this. Looking closer, there are a bunch of these environment variables that are undocumented, and they're also closely related to the mallopt() library function, which is also undocumented. I think it would be best to document all of this stuff together, and best done on a mallopt(3) page, rather that in the existing malloc(3). (And yes, the MALLOC_TRACE_ info that is currently in mallopt(3) should probably also move to the to-be-created mallopt(3) page.) I'll get onto this.

Thanks,

Michael

Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

[Bug 20102] malloc(3) should document MALLOC_PERTURB_ env option

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=20102

Michael Kerrisk <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         AssignedTo|documentation_man-pages@ker |[email protected]
                   |nel-bugs.osdl.org           |
Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html