public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexei dot khlebnikov at datacon dot at" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/654] Cancelling nptl thread on dlclose() leads to application hangup Date: Thu, 13 Jan 2005 12:31:00 -0000 [thread overview] Message-ID: <20050113123101.4802.qmail@sourceware.org> (raw) In-Reply-To: <20050112104719.654.alexei.khlebnikov@datacon.at> ------- Additional Comments From alexei dot khlebnikov at datacon dot at 2005-01-13 12:30 ------- I've tested the same testcase on another system, having kernel 2.4.20 and glibc 2.3.2 with linuxthreads. The program ran just fine. The test has been conducted today, 2004-01-13. The output: --- $ ./run loading ./libtestmod.so now Constructor called pureShutdown::func(void*) called hi there, new thread is up and running, thread id is 16386 Constructor finished = thread 16386 is still running... = thread 16386 is still running... = thread 16386 is still running... = thread 16386 is still running... unloading ./libtestmod.so now Destructor called modShutdown() called bye, cancelling down thread 16386 running pthread_join(g_tid, &result) ... returned from pthread_join(g_tid, &result) ! all's well that end's well modShutdown() finished Destructor finished $ --- System information: CPU: Intel(R) Xeon(TM) CPU 2.80GHz Distribution: SuSE Linux 8.2 Kernel: 2.4.20-64GB-SMP, from the SuSE distribution Glibc version: --- $ /lib/libc.so.6 GNU C Library stable release version 2.3.2, by Roland McGrath et al. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 3.3 20030226 (prerelease) (SuSE Linux). Compiled on a Linux 2.4.20 system on 2003-03-13. Available extensions: GNU libio by Per Bothner crypt add-on version 2.1 by Michael Glad and others linuxthreads-0.10 by Xavier Leroy NoVersion patch for broken glibc 2.0 binaries BIND-8.2.3-T5B libthread_db work sponsored by Alpha Processor Inc NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk Report bugs using the `glibcbug' script to <bugs@gnu.org>. --- GCC version: --- $ gcc -v Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux Thread model: posix gcc version 3.3 20030226 (prerelease) (SuSE Linux) --- Ld/Binutils version: --- $ ld -v GNU ld version 2.13.90.0.18 20030121 (SuSE Linux) --- -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=654 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-01-13 12:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-12 10:47 [Bug nptl/654] New: " alexei dot khlebnikov at datacon dot at 2005-01-12 10:49 ` [Bug nptl/654] " alexei dot khlebnikov at datacon dot at 2005-01-13 12:31 ` alexei dot khlebnikov at datacon dot at [this message] 2005-01-13 12:52 ` alexei dot khlebnikov at datacon dot at 2005-01-13 13:15 ` jakub at redhat dot com 2005-01-17 12:43 ` alexei dot khlebnikov at datacon dot at 2005-01-17 12:47 ` alexei dot khlebnikov at datacon dot at 2006-05-02 22:03 ` drepper at redhat dot com [not found] <bug-654-131@http.sourceware.org/bugzilla/> 2010-12-10 3:43 ` r0bertz at gentoo dot org 2010-12-10 12:51 ` r0bertz at gentoo dot org 2012-05-06 9:04 ` aj at suse dot de
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050113123101.4802.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).