This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Disallow pseudo-registers in agent expression.
- From: "Jim Blandy" <jimb at red-bean dot com>
- To: "andrzej zaborowski" <balrogg at gmail dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 5 Feb 2008 11:16:02 -0800
- Subject: Re: [PATCH] Disallow pseudo-registers in agent expression.
- References: <fb249edb0801261107s6444f842s45ef63860c38f4d3@mail.gmail.com> <fb249edb0801261110g75922f69o948a2e2fd6b08dfa@mail.gmail.com> <8f2776cb0801271007r125463e0la1cf8a7c9d1efef@mail.gmail.com> <fb249edb0801281551o68911a0cw5e6d2051247722ab@mail.gmail.com> <8f2776cb0801281728v2ff40d50y2be92664b2c28de5@mail.gmail.com> <8f2776cb0802050734x1f79a335kfa3eaa104f25fedc@mail.gmail.com> <fb249edb0802051022h6b976c99se22127748d070440@mail.gmail.com>
On Feb 5, 2008 10:22 AM, andrzej zaborowski <balrogg@gmail.com> wrote:
> As far as I understand it's still a change that requires implementing
> new bits in architecture code, because architectures don't know how to
> make bytecode for pseudo-registers right now.
That's right. The suggested patch I posted doesn't show this, but the
way to do it would be to make it a gdbarch method with a predicate
indicating whether the architecture provides the method or not (an 'M'
entry in gdbarch.sh; search for "M -> " in there for docs), and then
have ax-gdb.c check for the presence of the method, use it if present,
and throw an error otherwise. This would allow us to implement the
method only on the architectures on which some contributor was
motivated to implement it.
> Apart from little time I have zero knowledge about 95% of the
> architectures in gdb :(
Well, there are a lot of architectures. I think many of our
contributors know only a few.