[PATCH] Handle errors in tracepoint target agent
Stan Shebs
stan@codesourcery.com
Thu Mar 25 23:06:00 GMT 2010
Pedro Alves wrote:
> 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.
>
Ugh. Given that this is a file format, and more particularly a type of
file that we could get handed by users, I'm thinking I want to go back
and tweak GDB to not care about its value much, and only require it to
match the size of any fixed-size register blocks present in the trace file.
Stan
More information about the Gdb-patches
mailing list