You shot yourself in the foot right at the start. You can't return a pointer to memory on the stack and expect it to be valid when it goes out of scope.
Dear friends
I have a bit basic doubts in pointers and the structures inter relationships.
the first one.
static struct apvt {
int dead;
int pending;
int abouttograb;
}*agents=NULL;
what agents pointer is... (1 Reply)
Hi All,
I was given a format of a file, and was asked to write a program which displays the data contained in the file in that purticular format.
Its all so confusing.
Please find the example of the format as well the code I have written in the attachment.
I hope any one of u guyz can... (0 Replies)
Hi all!
I am working on unix systems.I am programming in c.
I have got some problems with pthread.when I use pthread_create to creat a thread it says:
(.text+0x3a): undefined reference to `pthread_create'.
same is the problm with pthread_kill.
Can anyone help me out here.
Thanks.
vij. (2 Replies)
hello
can any1 plz tell me about the system defined structures (like sysinfo) which wil give system and n/w charecteristics (ex: freeram in sysinfo). (1 Reply)
Hello,
I run my pthread code on Linux with 4 processors. However, the speed up is only 2 times.
The code is about solving equation (G+s(i)C)z(i)=B*us(i), i=1,...,n. Here G,C are m*m matrix, B*us(i) is a m*1 vector and s(i) are n different numbers. I need to solve the equation n times to... (2 Replies)
Hi All,
I am using the array of pointers and storing the address of string.This is a global list.
So i am using extern to give the reference of this list to another file and using reading the data from this string.
But list is being corrupted and string is missing some characters in... (2 Replies)
Hi all,
I wrote some code in c, using pthread (I configured the linker and compiler in eclipse IDE first).
#include <pthread.h>
#include "starter.h"
#include "UI.h"
Page* MM;
Page* Disk;
PCB* all_pcb_array;
void* display_prompt(void *id){
printf("Hello111\n");
return... (1 Reply)
Hello All,
I am having this issue...where I am actually having hard time understanding the problem:
The code is as follows:
#include<iostream.h>
void fxn(char*** var)
{
int i =4;
*var = (char**)malloc(i*sizeof(char*));
for(int j =0; j<4; j++)
{
*var = "name";
cout<<*var;... (6 Replies)
Hello,
I have a signal handler which manipulates a data structure. The data structure's operations aren't atomic. So if two threads/processes are in a critical section at the same time the data structure will be broken.
With threads you can avoid this stuff with semaphores etc.
However,... (10 Replies)
Discussion started by: littlegnome
10 Replies
LEARN ABOUT HPUX
pthread_mutex_destroy
pthread_mutex_init(3T)pthread_mutex_init(3T)NAME
pthread_mutex_init(), pthread_mutex_destroy() - initialize or destroy a mutex
SYNOPSIS PARAMETERS
mutex Pointer to the mutex to be initialized or destroyed.
attr Pointer to the attributes object that defines the characteristics of the mutex to be initialized. If the pointer is NULL,
default attributes are used.
DESCRIPTION
The function initializes the mutex referenced by mutex with the attributes attr. If the parameter attr is NULL, the default mutex
attributes are used. See pthread_mutexattr_init(3T) for a list of default mutex attributes. After successful initialization, the mutex is
initialized, unlocked, and ready to be used in mutex operations. A mutex should be initialized only once or the resulting behavior is
undefined. The function provides a way to ensure that a mutex is initialized only once.
The macro can be used to initialize mutexes that are statically allocated. These mutexes will be initialized with default attributes. The
function does not need to be called for statically initialized mutexes.
If the process-shared attribute in the mutex attributes object referenced by attr is defined as the mutex must be allocated such that the
processes sharing the mutex have access to it. This may be done through the memory-mapping functions (see mmap(2)) or the shared memory
functions (see shmget(2)).
The function destroys the mutex referenced by mutex. This function may set mutex to an invalid value. The destroyed mutex can be reini-
tialized using the function If the mutex is used after destruction in any mutex call, the resulting behavior is undefined.
A mutex should be destroyed only when it is unlocked. Destroying a mutex that is currently being used results in undefined behavior.
RETURN VALUE
Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
If any of the following occur, the function returns the corresponding error number:
The necessary resources (other than memory) to initialize
mutex were not available.
mutex is an already initialized mutex. However, getting for reinitializing the mutex cannot be expected all the time since
the behavior of reinitializing the mutex is undefined.
mutex points to an illegal address.
The value specified by
mutex or attr is invalid.
There is insufficient memory available in which to initialize
mutex.
The caller does not have the necessary permission to perform the
mutex initialization.
If any of the following occur, the function returns the corresponding error number:
mutex is currently locked or in use by another thread.
mutex is not a valid mutex.
WARNINGS
The space for the mutex must be allocated before calling Undefined behavior will result if the process-shared attribute of attr is and the
space allocated for the mutex is not accessible to cooperating threads.
AUTHOR
and were derived from the IEEE POSIX P1003.1c standard.
SEE ALSO pthread_mutex_lock(3T), pthread_mutex_trylock(3T), pthread_mutex_unlock(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_mutex_init(3T)