From: Daniel Jacobowitz <drow@false.org>
To: Craig Silverstein <csilvers@google.com>
Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org
Subject: Re: Patch to handle compressed sections
Date: Wed, 02 Apr 2008 12:27:00 -0000 [thread overview]
Message-ID: <20080402001637.GA18178@caradoc.them.org> (raw)
In-Reply-To: <20080402000638.1BD1B3F25EF@localhost>
On Tue, Apr 01, 2008 at 05:06:38PM -0700, Craig Silverstein wrote:
> My plan is to name the new sections .zdebug_foo. They will start with
> a 5-byte header that indicates what compression format is being used,
> and what version of the format. For now, only ZLIB1 will be
> supported.
>
> Following the ZLIB1 header-field will be an 8-byte length
> header-field, in big-endian order -- I know DWARF mostly uses leb128,
> but I don't want to add the complexity for people who just want to
> parse the header (which, technically, isn't part of dwarf :-) ).
> Plus, we don't care much about the space used here.
>
> Following the length will come the content, which is just a blob of
> data compressed by zlib.
>
> gdb will be changed to look for .zdebug_foo as an alternate to
> .debug_foo, and the section-reading code will decompress such sections
> at read-time.
>
> Does this sound like a reasonable plan? If so, I'll try to get a new
> patch later this week.
Yes, it sounds reasonable - give it a few days in case anyone else has
comments? I would have made different choices, but they're not
inherently superior.
(I'd have used a four-byte magic, and an object-file-endianness 64-bit
size; in particular the four-byte magic makes it easier to visually
see the size in section dumps.)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-02 0:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 23:05 Craig Silverstein
2008-03-26 16:10 ` Thiago Jung Bauermann
2008-03-26 17:40 ` Craig Silverstein
2008-03-26 18:01 ` Daniel Jacobowitz
2008-03-26 18:36 ` Craig Silverstein
2008-04-01 14:28 ` Daniel Jacobowitz
2008-04-02 0:38 ` Craig Silverstein
2008-04-02 12:27 ` Daniel Jacobowitz [this message]
2008-04-02 12:51 ` Craig Silverstein
2008-04-02 14:13 ` Andreas Schwab
2008-04-03 7:38 ` Craig Silverstein
2008-04-03 8:45 ` Craig Silverstein
2008-04-03 11:01 ` Pedro Alves
2008-04-03 11:10 ` Pedro Alves
2008-04-03 21:43 ` Craig Silverstein
2008-04-04 1:28 ` Craig Silverstein
2008-04-15 6:16 ` Craig Silverstein
2008-04-17 16:24 ` Daniel Jacobowitz
2008-04-17 20:57 ` Craig Silverstein
2008-04-17 21:09 ` Daniel Jacobowitz
2008-04-19 0:32 ` Craig Silverstein
2008-04-19 0:13 ` Daniel Jacobowitz
2008-04-19 0:32 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080402001637.GA18178@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=csilvers@google.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox