This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hello,
I'm not sure what you mean here. Your simulator can send back a short G packet that contains just the GPR and FPU registers.It also appears that the powerpc:common architecture setting has added the AltiVec register set sometime between gdb 5.1 and the latest version. Consequently I am unable to have a "common" target in my simulator that works with various versions of gdb.
Is there a way for gdb to let the remote target know what registers it willSee:
be expecting for the read and write register commands? If not, would it be
worthwhile to add one? It would be helpful to know the name, size, and
order of all registers that will be used for the current debugging
session. Without knowing much about the remote debugging protocol,
something like the following might work:
query register info support: qRegInfo?
response: OK - willing to accept register info
'' - not willing to accept register info
send register info qRegInfo:n,s;n,s;
Where 'n' is the name of the register
being defined, and 's' is the size, in
bytes, of this register. The order is
the order within the read/write register command.
response : OK - all is understood
E?? - This target cannot work with the
current gdb architecture.
Figuring out which registers to expedite is, unfortunatly, a black art.p.s. It would also be useful to know the registers that are required for the expedited response from the target.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |