Bug 31365
| Summary: | malloc.3: malloc(3) and calloc(3) don't free memory, do they? | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Documentation | Reporter: | koich <koich> | ||||
| Component: | Books & Articles | Assignee: | freebsd-doc (Nobody) <doc> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
State Changed From-To: open->closed Applied, thanks! |
According to the man page of malloc.3 (rev 1.25.2.12): --- DIAGNOSTIC MESSAGES : The following is a brief description of possible warning messages and their meanings: : pointer to wrong page The pointer that malloc() or calloc() is trying to free does not reference a possible page.--- This warning message is output by irealloc() and free_pages() in malloc.c, and these two functions are called by realloc(), free() and reallocf(). (I'm looking src/lib/libc/stdlib/malloc.c,v 1.49.2.3 and src/lib/libc/stdlib/reallocf.c,v 1.3)