Submit #1398
open
hdestroy(3) restricts hash key to point to malloc'ed space
Added by Anonymous over 15 years ago.
Updated over 3 years ago.
Description
Salute.
hdestroy(3) frees the memory pointed to by the hash key. In other words it expects the user to always have malloc()'ed rather than used static allocation for the hash key. This doesn't apply to the data associated with the key.
Although POSIX standard doesn't say much on this particular topic:
- This is unnecessarily restrictive. If the user wants static allocation, we should allow this. If she wants dynamic then let her free the memory she malloc()'ed.
- It is in conflict with the example code in the POSIX page. The code segfaults if you add an hdestroy() call in the end of it.
- Programs that target other implementations may segfault in DragonFly (that'show I discovered it). AFAIK sunOS 5.10 and a recent glibc work fine, whereas {Net, Free, DragonFly}BSD all are affected because they share the same code. (One could argue that all programs written with the *BSD version in mind would
result in a memory leak. But still I think these programs (if any) should be fixed.)
Any thoughts ?
Cheers,
Stathis
Files
hdestroy(3) frees the memory pointed to by the hash key. In other words it
expects the user to always have malloc()'ed rather than used static allocation
for the hash key. This doesn't apply to the data associated with the key.
Any thoughts about this one ?
If no objections are raised, I'm going to push it in ~1 week.
Cheers,
Stathis
hdestroy(3) frees the memory pointed to by the hash key. In other words it
expects the user to always have malloc()'ed rather than used static allocation
for the hash key. This doesn't apply to the data associated with the key.
Any thoughts about this one ?
If no objections are raised, I'm going to push it in ~1 week.
I'll tweak the example in the man page, add a few words in the text and commit it.
Reviewed by dillon@ and hasso@.
Cheers,
Stathis
:Stathis Kamperis <ekamperi@gmail.com> added the comment:
:
:> hdestroy(3) frees the memory pointed to by the hash key. In other words i=
:t
:> expects the user to always have malloc()'ed rather than used static alloc=
:ation
:> for the hash key. This doesn't apply to the data associated with the key.
:
:Any thoughts about this one ?
:If no objections are raised, I'm going to push it in ~1 week.
:
:Cheers,
:Stathis
Sure. Does anyone even use those functions any more? They aren't threadable.
-Matt
- Tracker changed from Bug to Submit
- Description updated (diff)
- Category set to Userland
- Status changed from New to In Progress
- Target version set to 4.2
Moving to submit.
Still relevant.
- Target version changed from 4.2 to 6.0
- Description updated (diff)
Also available in: Atom
PDF
Updated by 
Updated by