From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11851 invoked by alias); 28 Nov 2006 19:34:16 -0000 Received: (qmail 11047 invoked by uid 48); 28 Nov 2006 19:34:02 -0000 Date: Tue, 28 Nov 2006 19:34:00 -0000 From: "sources dot redhat dot com at hovland dot cx" To: glibc-bugs@sources.redhat.com Message-ID: <20061128193401.3608.sources.redhat.com@hovland.cx> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug linuxthreads/3608] New: deadlock / race X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00097.txt.bz2 10 c++ threads throwing exception() every 0.1ms causes 100% cpu use (xeon x64 ht) and the threads stop responding. It doesnt happen right away but after random time (seconds). The same binary works fine on glibc-2.5+nptl (same kernel, same cpu). Kernel 2.6.18.1 -- Summary: deadlock / race Product: glibc Version: 2.3.6 Status: NEW Severity: normal Priority: P2 Component: linuxthreads AssignedTo: drow at false dot org ReportedBy: sources dot redhat dot com at hovland dot cx CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i686-j-linux GCC host triplet: i686-j-linux GCC target triplet: i686-j-linux http://sourceware.org/bugzilla/show_bug.cgi?id=3608 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.