don't use glibc malloc() and strdup() in lrc
Reported by virtuoso (at slind) | February 23rd, 2010 @ 12:27 AM
We actually can't use glibc calls that we directly or indirectly override in LRC code so as to avoid recursion and handlers messing up other handlers.
Comments and changes to this ticket
-
virtuoso (at slind) February 23rd, 2010 @ 12:37 AM
(from [02cf3c7bd95bad2662e561550c4bd8a1028bab99]) don't allocate log_output[]s [[#3] state:committed]
Since we can't really call libc where it will end up in one of our handlers.
It will be nice to have a simple internal allocator, but for now, this should
do.Signed-off-by: Alexander Shishkin virtuoso@slind.org
http://github.com/virtuoso/librandomcrash/commit/02cf3c7bd95bad2662... -
virtuoso (at slind) February 23rd, 2010 @ 12:38 AM
- State changed from “open” to “committed”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
People watching this ticket
virtuoso (at slind)
Tags
Referenced by
-
3
don't use glibc malloc() and strdup() in lrc
(from [02cf3c7bd95bad2662e561550c4bd8a1028bab99])
don't a...