From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13873 invoked by alias); 8 May 2003 13:25:44 -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 13866 invoked from network); 8 May 2003 13:25:44 -0000 Received: from unknown (HELO sun.netezza.com) (209.113.240.37) by sources.redhat.com with SMTP; 8 May 2003 13:25:44 -0000 Received: from astral (host20 [192.168.0.20]) by sun.netezza.com (8.12.9+Sun/8.12.9) with SMTP id h48DPh3b019745 for ; Thu, 8 May 2003 09:25:43 -0400 (EDT) Message-ID: <027701c31565$53c22b20$1400a8c0@astral> Reply-To: "John S. Yates, Jr." From: "John S. Yates, Jr." To: "gdb" Subject: info threads Date: Thu, 08 May 2003 13:25: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/msg00106.txt.bz2 I have been implementing support for "info threads" based on the stock 5.3 release. For the qfThreadInfo message I return a list of the addresses of all TCBs (thread control blocks) known to our nucleus. It turns out that some of these live below the 2GB boundary and some above. Only those TCBs that do not appear to be negative are displayed. Why is this? /john -- John S. Yates, Jr. 508 665-6897 (voice) Netezza Inc 508 665-6811 (fax) 200 Crossing Blvd. Framingham, MA 01701