This is the mail archive of the gdb@sourceware.org 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]

Re: [rfc/remote] Tell remote stubs which signals are boring


On Thu, Oct 26, 2006 at 02:28:38PM -0700, Jim Blandy wrote:
> Well, the numbers might be in the passive voice.  Or something.
> 
> I had in mind fixed-width vs. variable-width.  Fixed-width is used for
> signal numbers in the response packets, so I think there's room for
> confusion.  Signal numbers in the step and continue packets are
> documented to be variable-width hex, which is safely permissive; all
> I'm suggesting is that those two words be added.
> 
> I have run into width concerns working with other parts of the
> protocol (for example, with register values in T responses ---
> although that's target byte order so it's a bit different), so I think
> it's worth something to be explicit.

Ah, it's variable-width.  But the overview says this:

Except where otherwise noted all numbers are represented in HEX with
leading zeros suppressed.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]