From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25711 invoked by alias); 2 Feb 2003 21:04: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 25704 invoked from network); 2 Feb 2003 21:04:06 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.209.173) by 172.16.49.205 with SMTP; 2 Feb 2003 21:04:06 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 440E33CB1 for ; Sun, 2 Feb 2003 16:03:49 -0500 (EST) Message-ID: <3E3D87B5.9080306@redhat.com> Date: Sun, 02 Feb 2003 21:04:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: What to do with threads? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00031.txt.bz2 Hello, To put it simply, how can one fix this: static CORE_ADDR d10v_read_pc (ptid_t ptid) { .... read_register (PC_REGNUM); .... } There are problems at many levels. Off the top of my head: - ptid can identify a thread and/or a LWP - there sometimes isn't even a thread and/or a LWP - the selected and current thread both fight over the same global data structures - long long term, an objective is to have gdb debug multiple processes / ISAs - so long term that it is probably funny, an objective is to have gdb debugging multiple targets I think we've fought the frame battle and won (the casualties will take ages to recover mind :-), the thread battle, I think, is next. Andrew