From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5548 invoked by alias); 15 May 2003 16:53:04 -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 4480 invoked from network); 15 May 2003 16:52:34 -0000 Received: from unknown (HELO sun.netezza.com) (209.113.240.37) by sources.redhat.com with SMTP; 15 May 2003 16:52:34 -0000 Received: from astral (host20 [192.168.0.20]) by sun.netezza.com (8.12.9+Sun/8.12.9) with SMTP id h4FGqY3b016867 for ; Thu, 15 May 2003 12:52:34 -0400 (EDT) Message-ID: <049501c31b02$61f4e5f0$1400a8c0@astral> Reply-To: "John S. Yates, Jr." From: "John S. Yates, Jr." To: "gdb" Subject: unavailable register Date: Thu, 15 May 2003 16:53:00 -0000 Organization: Netezza Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-05/txt/msg00234.txt.bz2 I have been implementing thread support in a remote stub. My initial implementation provided only the values of the registers. I have now implemented register modification. One small glitch is that some registers are either architecturally readonly (eg: .sdata base register) or simple do not exist (eg: a blocking call into the scheduler does not save those registers that the calling conventions indicate are destroyable). My implementation of the 'P' message understands these issue and returns a failure where appropriate. Unfortunately, gdb's register cache seems to get updated before the 'P' message returns success. /john -- John S. Yates, Jr. 508 665-6897 (voice) Netezza Inc 508 665-6811 (fax) 200 Crossing Blvd. Framingham, MA 01701