From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29297 invoked by alias); 11 Oct 2004 16:17:24 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 29286 invoked from network); 11 Oct 2004 16:17:22 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 11 Oct 2004 16:17:22 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i9BGHCtN016831 for ; Mon, 11 Oct 2004 12:17:19 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i9BGH6r24759; Mon, 11 Oct 2004 12:17:06 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1DB1328CD; Mon, 11 Oct 2004 12:16:47 -0400 (EDT) Message-ID: <416AB1EE.9000706@gnu.org> Date: Mon, 11 Oct 2004 16:17:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20041009 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com, msnyder@redhat.com Subject: Re: [rfa] Include the LWP in thread-db's PTIDs References: <20041010213630.GA8218@nevyn.them.org> <416AA623.7080304@gnu.org> <20041011153838.GA26796@nevyn.them.org> In-Reply-To: <20041011153838.GA26796@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00196.txt.bz2 > I hadn't thought about the core issue; I'll do some pondering. However, > I don't think your comment is quite right. Thread_db can not be > layered over core files, we've already decided that - it's too iffy to > find the right thread_db, not to mention cross-debugging issues. And > similarly we can't use it for remote thread debugging. Thread_db only > makes any sense on top of local, running, native threads. "we"'ve definitly not decided this. Long ago you committed a hack to stop GDB layering thread-db over core files. It was to stop GDB barfing on native GNU/Linux core files. It had the side effect of breaking threads on all other systems, namely solaris. What keeps being pointing out is that thread-db should be loaded over a core file, and not doing it is broken. If we try it and it barfs, we've a bug. But what we've not got is an excuse for hobble native support (just because embedeed debuging is "iffy"). Andrew