From: Pedro Alves <pedro@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle errors in tracepoint target agent
Date: Thu, 25 Mar 2010 22:42:00 -0000 [thread overview]
Message-ID: <201003252242.05733.pedro@codesourcery.com> (raw)
In-Reply-To: <4BABE407.30609@codesourcery.com>
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
next prev parent reply other threads:[~2010-03-25 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 0:48 Stan Shebs
2010-03-25 4:18 ` Eli Zaretskii
2010-03-25 10:27 ` Pedro Alves
2010-03-25 22:30 ` Stan Shebs
2010-03-25 22:42 ` Pedro Alves [this message]
2010-03-25 23:06 ` Stan Shebs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003252242.05733.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox