bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Strange thread termination problem


From: Duncan Palmer
Subject: Strange thread termination problem
Date: Thu, 23 Aug 2001 20:39:11 +0100

I'm having a strange and vexing problem in some code i'm trying to debug
at the moment... the problem occurs as a result of terminating a thread
soon after i've started it. The attached code is an attempt to write an
example which reproduces the problem - tho it fails in that goal (i
suspect because of timing issues), it does show roughly how i've been
able to hack my application to make the problem occur in a reproducable
fashion (before i hacked it up, the problem was occuring intermittently
as a result of me pressing a button on the screen at a crucial and
rather unpredictable time).

The problem is that when i terminate the thread that loop() is running
in, a SIGABRT gets sent by something down in the pthread library. This
SIGABRT gets sent during the pthread_mutex_lock() call in the test_class
destructor... When i run the application on an x86 machine (my dev
target is a StrongARM SA1110), the message 'pure virtual method called'
also gets spat out at me when things go wrong... - in my actual
implementation, the destructor which calls pthread_cancel() is in a
subclass of the class i'm using, tho there are no pure virtual
destructors anywhere...

I'm using glibc-2.1.3 , libstdc++-libc6.1-2.so.3 and libpthread0.8 .

If anyone has any thoughts, i'd really appreciate it.

Cheers,
Dunk

-- 
Duncan Palmer                                    
address@hidden
Software Design Engineer                          Phone:    
+353-1-2911561
Silicon and Software Systems                      Fax:      
+353-1-2911001

Attachment: main.c
Description: application/unknown-content-type-cfile


reply via email to

[Prev in Thread] Current Thread [Next in Thread]