From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26601 invoked by alias); 7 Sep 2004 10:49:05 -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 26594 invoked from network); 7 Sep 2004 10:49:04 -0000 Received: from unknown (HELO smtp.hispeed.ch) (62.2.95.247) by sourceware.org with SMTP; 7 Sep 2004 10:49:04 -0000 Received: from indel.ch (217-162-27-127.dclient.hispeed.ch [217.162.27.127]) by smtp.hispeed.ch (8.12.6/8.12.6/tornado-1.0) with SMTP id i87An36i030970 for ; Tue, 7 Sep 2004 12:49:03 +0200 Received: from fabi.indel.ch [192.168.1.19] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Tue, 07 Sep 2004 12:46:39 +0200 Message-Id: <5.2.0.9.1.20040907124018.01d3f280@NT_SERVER> X-Sender: cenedese@NT_SERVER (Unverified) Date: Tue, 07 Sep 2004 10:49:00 -0000 To: gdb@sources.redhat.com From: Fabian Cenedese Subject: thread id width Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gdb@sources.redhat.com X-Return-Path: cenedese@indel.ch X-SW-Source: 2004-09/txt/msg00048.txt.bz2 Hi Some MI commands work with a 16bit hex encoded thread id (e.g. qC). But then there's also qPmodethreadid where threadid is a 64bit value. And some commands don't mention the size at all (vCont, TXX). Is the limitation to 16bit still mandatory? Are there places in gdb that can't cope with bigger ids? If so, why does the qP work with 64bit? For being future-save? Thanks bye Fabi