|
Hello
Venkata:
It
seems that your memory has probably been corrupted before making this call, or
that the data being passed into the call is bad. These functions get used
a lot so I doubt theres any problem with them, but it isn't something too easily
debuggable from the core. This is similar to your last message re: a
malloc() segmentation fault. I would make sure no recently free()'d memory
has been referenced or any sort of memory issue like that.
Randy
Hello all,
This is regarding a query on
pthead_cond_timedwait..
I have received SIGSEGV from
pthread_cond_timedwait.
It seems that libc has
sent this signal. I would like to know
has any one faced this problem?or am I missing
something.
Can any one tell me the situations where this
can happen.
Following are the back traces from
gdb
------------------------------------------------
Reading symbols from
/lib/libpthread.so.0...done.
Reading symbols from
/lib/libc.so.6...done.
Reading symbols from
/lib/ld-linux.so.2...done.
Reading symbols from
/lib/libnss_files.so.2...done.
#0 0x401977f1 in __libc_nanosleep ()
from /lib/libc.so.6
(gdb) bt
#0 0x401977f1 in __libc_nanosleep ()
from /lib/libc.so.6
#1 0x400fa429 in pthread_cond_timedwait
(cond=0x8051d20, mutex=0x8051d08,
abstime=0xbefffbb0)
at condvar.c:94
#2 0x400d3772 in OS_GetTimerSignal
(signalParam=0xbefffd00)
at
osSpecific.c:1290
#3 0x400b6e19 in timerThread (info=0x400ee018) at
timerThread.c:93
#4 0x400faeca in pthread_start_thread
(arg=0xbefffe60) at manager.c:213
(gdb)
Thanks,
Rajesh.
|
