Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yes, I think this is accurate:

https://www.gnu.org/software/bash/manual/html_node/Optional-...

> --with-bash-malloc

> Use the Bash version of malloc in the directory lib/malloc. This is not the same malloc that appears in GNU libc, but an older version originally derived from the 4.2 BSD malloc. This malloc is very fast, but wastes some space on each allocation. This option is enabled by default. The NOTES file contains a list of systems for which this should be turned off, and configure disables this option automatically for a number of systems.

> --with-gnu-malloc

> A synonym for --with-bash-malloc.

http://git.savannah.gnu.org/cgit/bash.git/tree/NOTES?h=devel

> Platform-Specific Configuration and Operation Notes [very dated]

> 1. configure --without-gnu-malloc on:

> alpha running OSF/1, Linux, or NetBSD (malloc needs 8-byte alignment;

> bash malloc has 8-byte alignment now, but I have no alphas to test on)

> next running NeXT/OS; machines running Openstep

> all machines running SunOS YP code: SunOS4, SunOS5, HP/UX, if you have problems with username completion or tilde expansion for usernames found via YP/NIS

> linux (optional, but don't do it if you're using Doug Lea's malloc)

> QNX 4.2

> other OSF/1 machines (KSR/1, HP, IBM AIX/ESA)

> AIX

> sparc SVR4, SVR4.2 (ICL reference port)

> DG/UX

> Cray

> Haiku OS

> NetBSD/sparc (malloc needs 8-byte alignment; bash malloc has 8-byte alignment now, but I have no NetBSD machines to test on)

> BSD/OS 2.1, 3.x if you want to use loadable builtins

> Motorola m68k machines running System V.3. There is a file descriptor leak caused by using the bash malloc because closedir(3) needs to read freed memory to find the file descriptor to close



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: