From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14716 invoked by alias); 11 Dec 2002 22:55:37 -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 14709 invoked from network); 11 Dec 2002 22:55:36 -0000 Received: from unknown (HELO hydra.ubicom.com) (4.20.168.98) by sources.redhat.com with SMTP; 11 Dec 2002 22:55:36 -0000 Received: FROM jaguar.scenix_engr BY hydra.ubicom.com ; Wed Dec 11 14:54:17 2002 -0800 Received: from ubicom.com by jaguar.scenix_engr (SMI-8.6/SMI-SVR4) id OAA12783; Wed, 11 Dec 2002 14:55:25 -0800 Received: (from natg@localhost) by ubicom.com (8.11.6/8.11.6) id gBBMtPL08351; Wed, 11 Dec 2002 14:55:25 -0800 Date: Wed, 11 Dec 2002 14:55:00 -0000 From: Nat Gurumoorthy Message-Id: <200212112255.gBBMtPL08351@ubicom.com> To: ac131313@redhat.com Subject: Re: Proposal for customization of output of "to_pid_to_str" op in remote.c Cc: gdb@sources.redhat.com X-SW-Source: 2002-12/txt/msg00184.txt.bz2 >Andrew Cagney Wrote >Er, isn't there already stuff like qThreadInfo? Andrew, qThreadInfo only lets the remote pass back target thread IDs to GDB. GDB then converts the pid into and GDB internal ptid (process + thread ID). The "to_pid_to_str" function pointer in the target structure is used to convert a ptid to a printable string. If you are currently using the remote interface this defaults to looking like "Thread 1" "Thread 2" etc. I would like the the target to be print whatever it wants. Regards Nat