Bug 185502 - Values for MALLOC_CHECK_ env variable differs in different documentation
Summary: Values for MALLOC_CHECK_ env variable differs in different documentation
Alias: None
Product: Fedora
Classification: Fedora
Component: man-pages   
(Show other bugs)
Version: 3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-15 10:03 UTC by Nigel Horne
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-16 11:43:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Nigel Horne 2006-03-15 10:03:35 UTC
Description of problem:

Discrepancy between the release notes and man page for malloc

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. View file:///usr/share/doc/HTML/index.html with a browser
2. Look for the section on glibc
3. Run "man malloc"
Actual results:
Release notes claim for malloc_check:

      0 â Do not generate an error message, and do not kill the program

      1 â Generate an error message, but do not kill the program

      2 â Do not generate an error message, but kill the program

      3 â Generate an error message and kill the program

man malloc claims for malloc_check:
 If  MALLOC_CHECK_  is  set  to  0,  any  detected heap corruption is silently
       ignored; if set to 1, a diagnostic is printed on stderr; if set to  2,
       abort() is called immediately. 

Expected results:

Additional info:

Comment 1 Jakub Jelinek 2006-03-15 17:07:58 UTC
rpm -qf /usr/share/man/man3/malloc.3.gz

Comment 2 Ivana Varekova 2006-03-16 11:43:04 UTC
Thank you for your bug report, the malloc man page is fixed in man-pages-2.25-2.

Note You need to log in before you can comment on or make changes to this bug.