[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [llnl-devel] Re: [Freeipmi-devel] kcs byte array model - validation
From: |
Ian Zimmerman |
Subject: |
Re: [llnl-devel] Re: [Freeipmi-devel] kcs byte array model - validation |
Date: |
15 Dec 2003 15:58:39 -0800 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
> > This may be true, with respect to signal handlers and call-back
> > procedures. But I'm skeptic about malloc usage inside library. Because
> > malloc, free uses static references inside, there is no way to
> > guarantee the buffer returned really belongs to the last call of the
> > current thread in a multi-threaded environment. I have seen some
> > references mentioning malloc is thread safe!. On all platforms and
> > implementations ?
>
> I believe that your information regarding this topic is out of date and
> that if you grep through the source code of many libraries included with
> linux and other operating systems you will find that they do not worry
> about using malloc and free. This includes libraries that have been
> widely ported such as glib.
Right. thread-safe != reentrant. This is discussed in some detail in
Rich Stevens' APUE book (among other places).
Ian
- [Freeipmi-devel] Get IPMI device info code - 1st cut, RFC, (continued)
- [Freeipmi-devel] Get IPMI device info code - 1st cut, RFC, Ian Zimmerman, 2003/12/11
- Re: [Freeipmi-devel] Get IPMI device info code - 1st cut, RFC, Anand Babu, 2003/12/11
- Re: [Freeipmi-devel] Get IPMI device info code - 1st cut, RFC, Ian Zimmerman, 2003/12/11
- Re: [Freeipmi-devel] Get IPMI device info code - 1st cut, RFC, Anand Babu, 2003/12/12
Re: [Freeipmi-devel] kcs byte array model - validation, Albert Chu, 2003/12/10
Re: [Freeipmi-devel] kcs byte array model - validation, Anand Babu, 2003/12/11
Re: [Freeipmi-devel] kcs byte array model - validation, Albert Chu, 2003/12/11