RE: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96

RE: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96

[Eljay Love-Jensen]

Hi Jyotirmoy,

I do not know if that list is comprehensively sufficient for Red Hat Linux 
Advanced Server 2.1.  (I use RHLAS 2.1, but not for a multithreaded 
application.)

I presume you are including the correct flag for multithreading.  That 
would be "gcc -pthread" for compile and link (which puts in -D_REENTRANT 
and -lpthread, respectively).  Da?  Nyet?

And I presume your GCC was built with --enable-threads=posix (which you can 
see via "gcc -v" for GCC 3.2, but I presume you'll have to infer during 
compilation if you use RH/GCC 2.96).

In C and C++, multithreading is wishy-washy.  It's not part of the 
language, it's a "bolt-on" that varies by vendor.  And not all vendors or 
platforms support POSIX (or necessarily support POSIX correctly).

For C++, I believe the BOOST folks have a platform-neutral thread 
API.  Assuming you were using C++, it's probably a little late in the game 
to switch horses to a different thread paradigm (say, BOOST versus POSIX or 
versus platform-centric).

HTH,
--Eljay

RE: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96

[Jyotirmoy Das]

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

Re: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96

[Eljay Love-Jensen]

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

noreentrant functions on Linux Advance Server 2.1 using gcc 2.96

[Jyotirmoy Das]

Hi All, 
  How can I get the list of thread unsafe functions on Linux Advance
Server 2.1 using gcc 2.96? And also how to get their corresponding
thread safe version? 
How I know that I particular function is reentrant or not?

Thanks,
Jyotirmoy