From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16782 invoked by alias); 4 Feb 2009 13:09:32 -0000 Received: (qmail 16767 invoked by alias); 4 Feb 2009 13:09:31 -0000 Date: Wed, 04 Feb 2009 13:09:00 -0000 Message-ID: <20090204130931.16766.qmail@sourceware.org> From: "pedro at codesourcery dot com" To: gdb-prs@sourceware.org In-Reply-To: <20090204120332.9817.mihai.stanescu@gmail.com> References: <20090204120332.9817.mihai.stanescu@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug threads/9817] GDB goes to 100% CPU usage indefinitely if pthread stack address is modified X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2009-q1/txt/msg00249.txt.bz2 ------- Additional Comments From pedro at codesourcery dot com 2009-02-04 13:09 ------- Subject: Re: New: GDB goes to 100% CPU usage indefinitely if pthread stack address is modified Hi, On Wednesday 04 February 2009 12:03:33, mihai dot stanescu at gmail dot com wrote: > The particular thing about the program is that is doing a pthread_attr_setstack > to setup the thread stack to a dynamically allocated memory area on heap. > > pthread_attr_setstack(&attr, alignedStackBase, THREAD_STACK_SIZE - > 2*PTHREAD_STACK_MIN) > Any chance you have a minimal test app you could attach that reproduce the problem? There have been numerous fixes since gdb 6.8. Could you please try what happens with a recent gdb snapshot (or cvs head)? Thanks, -- http://sourceware.org/bugzilla/show_bug.cgi?id=9817 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.