06-05-2012
I dont see :
[Thread debugging using libthread_db enabled]
Stack is corrupted, So
thread apply all bt
will provide some junk values.
info threads
will sometimes provide the list of threads.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
3. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
4. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
5. Programming
Could any one please suggest me how to solve this......
when I compiled the program and tried to execute it as follows, it works fine under different inputs like:
./main -r 300 -w 3 -s 100
./main -r 600 -w 3 -s 1000
./main -r 10 -w 3 -s 100
But it fails when I tired to give the input as... (1 Reply)
Discussion started by: kumars
1 Replies
6. AIX
Hi ,
I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information.
ux201p3:e46123> dbx capsWrkstnMgr core
Type 'help' for help.
reading symbolic information ...
Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies
7. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
8. Emergency UNIX and Linux Support
Hi,
I have got core dump stating "core.bash.29846" so i am unable to open.
How to open the core dump file for further analysis?
Reagards
Vanitha (7 Replies)
Discussion started by: vanitham
7 Replies
9. UNIX for Dummies Questions & Answers
Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
10. Red Hat
Hello All,
I am new joiner of this forum.I am new to Linux shell scripting.
At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
LEARN ABOUT OSX
pthread_setspecific
PTHREAD_SETSPECIFIC(3) BSD Library Functions Manual PTHREAD_SETSPECIFIC(3)
NAME
pthread_setspecific -- set a thread-specific data value
SYNOPSIS
#include <pthread.h>
int
pthread_setspecific(pthread_key_t key, const void *value);
DESCRIPTION
The pthread_setspecific() function associates a thread-specific value with a key obtained via a previous call to pthread_key_create(). Dif-
ferent threads may bind different values to the same key. These values are typically pointers to blocks of dynamically allocated memory that
have been reserved for use by the calling thread.
The effect of calling pthread_setspecific() with a key value not obtained from pthread_key_create(), or after key has been deleted with
pthread_key_delete(), is undefined.
pthread_setspecific() may be called from a thread-specific data destructor function; however, this may result in lost storage or infinite
loops.
RETURN VALUES
If successful, the pthread_setspecific() function will return zero. Otherwise, an error number will be returned to indicate the error.
ERRORS
pthread_setspecific() will fail if:
[EINVAL] The key value is invalid.
[ENOMEM] Insufficient memory exists to associate the value with the key.
SEE ALSO
pthread_getspecific(3), pthread_key_create(3), pthread_key_delete(3)
STANDARDS
pthread_setspecific() conforms to ISO/IEC 9945-1:1996 (``POSIX.1'').
BSD
April 4, 1996 BSD