From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Jacobowitz To: Andrew Cagney , gdb@sources.redhat.com Subject: Re: parcelling up struct gdbarch Date: Thu, 19 Jul 2001 00:23:00 -0000 Message-id: <20010719002318.A2129@nevyn.them.org> References: <3B533AAD.1060300@cygnus.com> <20010716130559.B25488@nevyn.them.org> <3B536764.1000508@cygnus.com> <20010716154904.A8712@nevyn.them.org> <3B547A08.2030403@cygnus.com> <20010717110305.A18932@nevyn.them.org> <3B5485C5.2010007@cygnus.com> <20010718132140.A2937@nevyn.them.org> <3B5675BA.4010403@cygnus.com> <20010718232242.A24417@nevyn.them.org> X-SW-Source: 2001-07/msg00274.html On Wed, Jul 18, 2001 at 11:22:42PM -0700, Daniel Jacobowitz wrote: > Well, implementation-wise and protocol-wise I'll need the same things > to do it hard-wired before I can do it flexibly, so I'm implementing > that structure now (I'm mostly done it, actually - I'm testing it for > mips32 now, and if it works I'll post it in the morning). > > Having flexible packet specs would remove a couple of trivial functions > that I wrote, but I'd prefer to tackle that idea after the remainder of > the issues have been dealt with. And it works. I currently move handling of the 'g' and 'G' packets off into the low-* file, which makes drastically more sense anyway. The code for prepare_resume_reply still needs to be handled, but the changes are trivial once the rest is in place. In remote.c, I add a 'qRegisters' packet with the reply 'qRegisters:IDENTIFIER', where IDENTIFIER is a (hex-encoded) defined name. It defines a register numbering, which remote.c takes care to use when talking to the target if one is available. The client-side changes are finished and I'll post them in the morning when I'm awake enough to write a proper changelog. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer