From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6914 invoked by alias); 8 Mar 2004 19:21:06 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6907 invoked from network); 8 Mar 2004 19:21:06 -0000 Received: from unknown (HELO rwcrmhc11.comcast.net) (204.127.198.35) by sources.redhat.com with SMTP; 8 Mar 2004 19:21:06 -0000 Received: from [192.168.0.1] (h00e098094f32.ne.client2.attbi.com[24.60.234.83]) by comcast.net (rwcrmhc11) with SMTP id <2004030819210501300df7ine> (Authid: houston.jim); Mon, 8 Mar 2004 19:21:05 +0000 Subject: Re: Making "info thread" sane From: Jim Houston Reply-To: jim.houston@comcast.net To: gdb@sources.redhat.com Content-Type: text/plain Organization: Message-Id: <1078773534.1180.102.camel@new.localdomain> Mime-Version: 1.0 Date: Mon, 08 Mar 2004 19:21:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00055.txt.bz2 George Anzinger wrote: > The problem is that, for most threaded apps and for the kernel which > treats each task as a thread, the "info thread" command gives a list > of threads all stopped in the context switch code. What is desired is > to do one or more "up" commands and report info on this location. Hi Everyone, I just posted a couple patches (on gdb-patches) which I did to support using kgdb on x86-64 linux. The one titled "thread info - automatic skip frames" addresses the problem George described above. My patch lets you list functions which should be automatically skipped when choosing a frame to display as part of the "info threads" command. e.g.: set skip-frame thread_return,schedule_timeout Jim Houston - Concurrent Computer Corp.