02-27-2009
Quote:
Originally Posted by
afroze
Thans 4 ur concern
My actual problem is below one. And iam not getting any idea please help me in this
" Developing a script to detect race conditions in a given library or code using multi-thread programming "
Script to detect race conditions in a given library or code? So you want something that will load the library or disassemble the library and search for possible race conditions? You also want that script to analyze plain code for race conditions? This is FAR from being simple. I'll post the possible solutions:
1) use some program (example: objdump) to disassemble the whole library and simply use regex to search for unsafe calls/interrupts.
2) load/use the library (dlopen/dlsym/dlclose) in thread1 and use thread2 to analyze calls for open() with ptrace() to check if there is any possible race condition.
3) Why is multi-threading an issue? Is this homework?
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'm currently writing a bash script, that starts multiple threads:
____________________
#!/bin/bash
loop=0
while((loop!=10))
do
thread &
((loop++))
done
#wait for all sub-processes (thread) to finish
wait
___________________
Now I want to know, what happens, if a... (2 Replies)
Discussion started by: tho99
2 Replies
2. Linux
In unix how we can test or check race condition in any c program by using multi thread programming (1 Reply)
Discussion started by: afroze
1 Replies
3. UNIX for Dummies Questions & Answers
In unix how we can test or check race condition in any c program by using multi thread programming (1 Reply)
Discussion started by: afroze
1 Replies
4. Programming
In unix how we can test or check race condition in any c program by using multi thread programming (1 Reply)
Discussion started by: afroze
1 Replies
5. Programming
I've been experimenting with pseudo-terminals and found something I don't quite understand. Writing an EOF character to the master end doesn't work quite as I expect. Once I've written any other data, the master pty seems to treat a single ^D as a seperator, i.e. writing "abcabc" would let cat do... (1 Reply)
Discussion started by: Corona688
1 Replies
6. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
7. Programming
Hi all,
i'm reading Andrew S.Tanenbaum's book --- Modern Operating System.At the part of discussing race condition.And the author gives a solution with using the TSL instruction,say that one process must call the enter_region function before entering the critical regions and call the leave_region... (0 Replies)
Discussion started by: homeboy
0 Replies
8. Shell Programming and Scripting
I want to make a script that check for the argument passed to it and generates an error in case any character/string argument passed to it.
I am using below code, but its not working. can anyone help.
#!/bin/bash
if ]; then
echo 'An integer argument is passed to the script hence... (3 Replies)
Discussion started by: mukulverma2408
3 Replies
9. Shell Programming and Scripting
I want to know the if condition in checking the hostname in unix and then running a cron job (all in a single line)
Thanks (2 Replies)
Discussion started by: prash358
2 Replies
LEARN ABOUT CENTOS
ares_library_init
ARES_LIBRARY_INIT(3) Library Functions Manual ARES_LIBRARY_INIT(3)
NAME
ares_library_init - c-ares library initialization
SYNOPSIS
#include <ares.h>
int ares_library_init(int flags)
cc file.c -lcares
DESCRIPTION
The ares_library_init function performs initializations internally required by the c-ares library that must take place before any other
function provided by c-ares can be used in a program.
This function must be called at least once within the life of a program, before the program actually executes any other c-ares library
function. Initializations done by this function remain effective until a number of calls to ares_library_cleanup(3) equal to the number of
calls to this function are performed.
Successive calls to this function do nothing further, only the first call done when c-ares is in an uninitialized state is actually effec-
tive.
The flags parameter is a bit pattern that tells c-ares exactly which features should be initialized, as described below. Set the desired
bits by ORing the values together. In normal operation you should specify ARES_LIB_INIT_ALL. Don't use any other value unless you are
familiar with it and trying to control some internal c-ares feature.
This function is not thread safe. You have to call it once the program has started, but this call must be done before the program starts
any other thread. This is required to avoid potential race conditions in library initialization, and also due to the fact that
ares_library_init(3) might call functions from other libraries that are thread unsafe, and could conflict with any other thread that is
already using these other libraries.
Win32/64 application DLLs shall not call ares_library_init(3) from the DllMain function. Doing so will produce deadlocks and other prob-
lems.
FLAGS
ARES_LIB_INIT_ALL
Initialize everything possible. This sets all known bits.
ARES_LIB_INIT_WIN32
Initialize Win32/64 specific libraries.
ARES_LIB_INIT_NONE
Initialize nothing extra. This sets no bit.
RETURN VALUE
Upon successful completion, ares_library_init() will return 0. Otherwise, a non-zero error number will be returned to indicate the error.
Except for ares_strerror(3), you shall not call any other c-ares function upon ares_library_init(3) failure.
AVAILABILITY
This function was first introduced in c-ares version 1.7.0 along with the definition of preprocessor symbol CARES_HAVE_ARES_LIBRARY_INIT as
an indication of the availability of this function. Its recursive behavior, which requires a matching number of calls to
ares_library_cleanup() in order to deinitialize the library, is present since c-ares version 1.10.0. Earlier versions would deinitialize
the library on the first call to ares_library_cleanup().
Since the introduction of this function it is absolutely mandatory to call it for any Win32/64 program using c-ares.
Non-Win32/64 systems can still use c-ares version 1.7.0 without calling ares_library_init(3) due to the fact that currently it is nearly a
do-nothing function on non-Win32/64 platforms at this point.
SEE ALSO
ares_library_cleanup(3), ares_strerror(3)
AUTHOR
Yang Tse
Copyright 1998 by the Massachusetts Institute of Technology.
Copyright (C) 2004-2009 by Daniel Stenberg.
19 May 2009 ARES_LIBRARY_INIT(3)