Re: [RFC] Enable GDB handle compressed target.xml returned by GDB stub

Jonathan Larmour
2012-06-13T13:47:22Z

On 13/06/12 14:12, Ulrich Weigand wrote:
> Terry Guo wrote:
>
>> Yes, we need to consider xi:includes which means we have to involve a
>> global state.
>
> Not necessarily; the way I had intended my suggestion to work was that
> GDB always adds ".gz" (or some other suffix if we actually are not
> compatible with the .gz file format) to *every* file it fetches, not
> just to the initial target.xml, but also to other files fetched via
> xi:include statements ...
>
> If the compressed version of the file is not available, GDB would
> then fall back to the original file name (on a file-by-file basis).

I agree.

This also means that the target can choose whether to return any file as
compressed or not, rather than having to have everything compressed from
then on, even if some XML files might take up more space compressed than
uncompressed, or might need to be generated - but not all files. It's
getting a bit hypothetical at this point, it's true, but not unreasonably so.

Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine