From: "Jan Beulich" <JBeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "Binutils" <binutils@sourceware.org>,"GDB" <gdb@sourceware.org>
Subject: Re: RFC: Add support for SHF_COMPRESSED
Date: Fri, 13 Mar 2015 16:19:00 -0000 [thread overview]
Message-ID: <55031C360200007800069EAF@mail.emea.novell.com> (raw)
In-Reply-To: <CAMe9rOoy9dbAw7Kh9+-haTE4gj4331Dk5E1YAr+1Xx+HBzCF0w@mail.gmail.com>
>>> On 13.03.15 at 17:13, <hjl.tools@gmail.com> wrote:
> On Fri, Mar 13, 2015 at 9:05 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> On 13.03.15 at 16:31, <hjl.tools@gmail.com> wrote:
>>> I am working on SHF_COMPRESSED support:
>>>
>>> http://www.sco.com/developers/gabi/latest/ch4.sheader.html
>>>
>>> We already have .zdebug* sections, which aren't compatible
>>> with SHF_COMPRESSED scheme due to missing compression
>>> header. What section names should we use for SHF_COMPRESSED
>>> debug sections. Using .debug* or .zdebug* will break existing tools.
>>> I am thinking .zlibdebug* or ..Zdebug*. Any suggestions?
>>
>> Why would they need to have different names anyway? They're
>> distinguishable by the flag.
>
> Won't the exiting tools, like GDB, choke on compressed .debug* sections?
If they're well behaved, they shouldn't (they should just ignore
them).
Jan
next prev parent reply other threads:[~2015-03-13 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 15:31 H.J. Lu
2015-03-13 16:05 ` Jan Beulich
2015-03-13 16:13 ` H.J. Lu
2015-03-13 16:19 ` Jan Beulich [this message]
2015-03-18 21:29 ` H.J. Lu
2015-03-19 18:19 ` Cary Coutant
2015-03-19 18:50 ` H.J. Lu
2015-03-20 9:01 ` Pedro Alves
2015-03-20 12:07 ` H.J. Lu
2015-03-20 13:36 ` H.J. Lu
2015-03-23 12:31 ` H.J. Lu
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=55031C360200007800069EAF@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).