Sponsored Content
Full Discussion: Thread Safe and Rentrancy
Top Forums Programming Thread Safe and Rentrancy Post 302722163 by Corona688 on Friday 26th of October 2012 11:54:06 AM
Old 10-26-2012
That article is clear as mud. How in the world is one thread going to make two simultaneous calls?

So just forget about threads for the moment. Re-entrant means you could call AddToString in main(), and in the middle of it, your program gets SIGUSR1 or something, and you have an interrupt handler configured for it. The software interrupt freezes your program and executes its own function until done -- and it uses AddToString too. Both calls end up adding the character as the first in the string because the first call hadn't managed to update length yet.

A re-entrant subroutine has to be able to handle these situations gracefully. Often that's done by just avoiding the problem completely -- not using global data of any sort, which prevents both things from competing. If they're not stomping on each other's data it's safe. It wouldn't even need to be mutexed anymore.

Otherwise, you might need to use atomic operations in a very carefully considered way to guarantee neither stomps on the other's variables.
This User Gave Thanks to Corona688 For This Post:
 

We Also Found This Discussion For You

1. Programming

compiling thread safe c on aix

Hi, I'm trying to compile a Perl module for AIX 5.3. Now, Perl by default wants to use cc_r as compiler but I only have gcc installed on this system. How can I get gcc to be thread safe? Or can I use gcc without any options and expect it to behave the same as cc_r? (0 Replies)
Discussion started by: rein
0 Replies
TTYNAME(3P)						     POSIX Programmer's Manual						       TTYNAME(3P)

PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond- ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. NAME
ttyname, ttyname_r - find the pathname of a terminal SYNOPSIS
#include <unistd.h> char *ttyname(int fildes); int ttyname_r(int fildes, char *name, size_t namesize); DESCRIPTION
The ttyname() function shall return a pointer to a string containing a null-terminated pathname of the terminal associated with file descriptor fildes. The return value may point to static data whose content is overwritten by each call. The ttyname() function need not be reentrant. A function that is not required to be reentrant is not required to be thread-safe. The ttyname_r() function shall store the null-terminated pathname of the terminal associated with the file descriptor fildes in the charac- ter array referenced by name. The array is namesize characters long and should have space for the name and the terminating null character. The maximum length of the terminal name shall be {TTY_NAME_MAX}. RETURN VALUE
Upon successful completion, ttyname() shall return a pointer to a string. Otherwise, a null pointer shall be returned and errno set to indicate the error. If successful, the ttyname_r() function shall return zero. Otherwise, an error number shall be returned to indicate the error. ERRORS
The ttyname() function may fail if: EBADF The fildes argument is not a valid file descriptor. ENOTTY The fildes argument does not refer to a terminal. The ttyname_r() function may fail if: EBADF The fildes argument is not a valid file descriptor. ENOTTY The fildes argument does not refer to a terminal. ERANGE The value of namesize is smaller than the length of the string to be returned including the terminating null character. The following sections are informative. EXAMPLES
None. APPLICATION USAGE
None. RATIONALE
The term ``terminal'' is used instead of the historical term ``terminal device'' in order to avoid a reference to an undefined term. The thread-safe version places the terminal name in a user-supplied buffer and returns a non-zero value if it fails. The non-thread-safe version may return the name in a static data area that may be overwritten by each call. FUTURE DIRECTIONS
None. SEE ALSO
The Base Definitions volume of IEEE Std 1003.1-2001, <unistd.h> COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 TTYNAME(3P)
All times are GMT -4. The time now is 05:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy