Hi
Some commit in the last few weeks has broken the malloc() debug flags on RELENG_5. According to the
man page, a call to free() or realloc() with a modified pointer should cause a warning. Setting the
A flag in either /etc/malloc.conf or MALLOC_OPTIONS should turn this into an error.
However,
In the last episode (Mar 21), Bartosz Fabianowski said:
Some commit in the last few weeks has broken the malloc() debug flags
on RELENG_5. According to the man page, a call to free() or realloc()
with a modified pointer should cause a warning. Setting the A flag
in either /etc/malloc.conf or
You're not running as root, are you? The A flag is always set for
root or setuid processes as a security measure.
No, I am running as a normal user.
There hasn't been any changes to the malloc code in 5.x since 5.3.
I realize there shouldn't have been any changes and I also cannot find
In the last episode (Mar 21), Bartosz Fabianowski said:
You're not running as root, are you? The A flag is always set for
root or setuid processes as a security measure.
No, I am running as a normal user.
There hasn't been any changes to the malloc code in 5.x since 5.3.
I realize
The actual test in the malloc code reads:
if (malloc_abort || issetugid() || getuid() == 0 || getgid() == 0)
wrterror(p)
, so it may also trigger if your primary groupid is 0 (wheel). Just
being a member of the wheel group won't trigger it.
Thank you very much for pointing this out. I
