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 MOJAVE
dlclose
DLCLOSE(3) BSD Library Functions Manual DLCLOSE(3)
NAME
dlclose -- close a dynamic library or bundle
SYNOPSIS
#include <dlfcn.h>
int
dlclose(void* handle);
DESCRIPTION
dlclose() releases a reference to the dynamic library or bundle referenced by handle. If the reference count drops to 0, the bundle is
removed from the address space, and handle is rendered invalid. Just before removing a dynamic library or bundle in this way, any termina-
tion routines in it are called. handle is the value returned by a previous call to dlopen.
Prior to Mac OS X 10.5, only bundles could be unloaded. Starting in Mac OS X 10.5, dynamic libraries may also be unloaded. There are a cou-
ple of cases in which a dynamic library will never be unloaded: 1) the main executable links against it, 2) An API that does not supoort
unloading (e.g. NSAddImage()) was used to load it or some other dynnamic library that depends on it, 3) the dynamic library is in dyld's
shared cache.
RETURN VALUES
If dlclose() is successful, it returns a value of 0. Otherwise it returns -1, and sets an error string that can be retrived with dlerror().
SEE ALSO
dlopen(3) dlsym(3) dlerror(3) dyld(3) ld(1) cc(1)
Nov 6, 2006