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: Self-describing targets - a more concrete proposal


On Wed, Mar 29, 2006 at 01:26:36PM -0800, Jim Blandy wrote:
> > >    To reduce protocol overhead, a target may supply a special annex
> > > named `CHECKSUMS' that provides 160-bit SHA1 checksum values for the
> > > annexes it has available.  The `CHECKSUMS' annex contains a series of
> > > newline-terminated lines, each of which contains a 40-digit hexidecimal
> > > checksum, two spaces, and the name of an annex with the given checksum.
> > > Here is an example `CHECKSUM' annex:
> > >      68c94ffc34f8ad2d7bfae3f5a6b996409211c1b1  target.xml
> > >      0e8e850b0580fbaaa0872326cb1b8ad6adda9b0d  mmu.xml
> > >      00f22e5f971ccec05c2acce98caf8cff4343c8cf  fpu.xml
> >
> > Shouldn't we document how to generate a checksum for a file?
> 
> SHA-1 is the name of the specific hash function that must be used. 
> I'll clear this up.

I think what Eli would like us to mention here would be "GNU Coreutils
provides an sha1sum utility which produces output in this format". 
Makes sense to me.  GNU coreutils is fairly portable, and some other
platforms probably provide SHA-1 utilities, so I don't think folks will
have a big problem generating these; we could even build sha1sum with
GDB if it would be helpful, but I'd rather not import that much of
coreutils if I can avoid it.

-- 
Daniel Jacobowitz
CodeSourcery


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