This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96
- From: "Jyotirmoy Das" <Jyotirmoy_Das at infosys dot com>
- To: "Eljay Love-Jensen" <eljay at adobe dot com>
- Cc: <gcc-help at gcc dot gnu dot org>
- Date: Fri, 26 Mar 2004 18:23:36 +0530
- Subject: RE: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96
Hi Eljay,
Thanks for your reply.
I am currently using the link as you specified below. I want to know
specifically the exhausted function list on LAS 2.1. Is that list is
sufficient?
I have almost seven lacks lines of code. In addition, it is not possible
for me to go through the each of source file and as a result, I need the
list of functions so that I can use the list in a shell script to point
out the source files.
Moreover, Is malloc a thread-safe function?
Thanks,
Jyotirmoy
-----Original Message-----
From: Eljay Love-Jensen [mailto:eljay@adobe.com]
Sent: Friday, March 26, 2004 6:14 PM
To: Jyotirmoy Das; gcc-help@gcc.gnu.org
Subject: Re: noreentrant functions on Linux Advance Server 2.1 using gcc
2.96
Hi Jyotirmoy,
The thread unsafe ones are all the ones that return a pointer to an
internal buffer.
The corresponding thread safe versions have the same name with a suffix
of
_r (for "re-entrant").
For instance, ctime() and ctime_r().
Bionic Buffalo lists these thread safe / unsafe functions:
<http://www.tatanka.com/doc/technote/tn0105.pdf>
HTH,
--Eljay