From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30666 invoked by alias); 25 Mar 2010 22:42:14 -0000 Received: (qmail 30658 invoked by uid 22791); 25 Mar 2010 22:42:13 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 25 Mar 2010 22:42:09 +0000 Received: (qmail 27022 invoked from network); 25 Mar 2010 22:42:07 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 25 Mar 2010 22:42:07 -0000 From: Pedro Alves To: Stan Shebs Subject: Re: [PATCH] Handle errors in tracepoint target agent Date: Thu, 25 Mar 2010 22:42:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; ) Cc: gdb-patches@sourceware.org References: <4BAAB2E9.7020708@codesourcery.com> <201003251027.14862.pedro@codesourcery.com> <4BABE407.30609@codesourcery.com> In-Reply-To: <4BABE407.30609@codesourcery.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201003252242.05733.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-03/txt/msg00867.txt.bz2 On Thursday 25 March 2010 22:30:31, Stan Shebs wrote: > > FIXME? If not important, or if this just need to be as big enough > > to cope with all supported archs, then we should drop the FIXME note, > > and explain that instead. > > > I was thinking somebody might know of a clever way for the compiler to > get it into the test program... You could pass it down to gdb_compile as an extra #define from the .exp, using additional_flags for example: additional_flags=-DREGBLOCK_SIZE=$regblocksize Is there a way to query GDB for this size, so the .exp can get at it? If not, maybe we can add a maintenance command for this? A fixed size per target doesn't quite cut it, considering extended register sets, and target descriptions. -- Pedro Alves