From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: handle "MiniDebuginfo" section
Date: Fri, 09 Nov 2012 18:23:00 -0000 [thread overview]
Message-ID: <20121109182316.GQ5103@adacore.com> (raw)
In-Reply-To: <87wqxuel5k.fsf@fleche.redhat.com>
> Fedora recently approved and committed the "MiniDebuginfo" feature:
>
> http://fedoraproject.org/wiki/Features/MiniDebugInfo
Looks pretty nice :)
> This patch adds support for this feature to gdb. I think the
> implementation is pretty straightforward. If you want to enable it, you
> will need the LZMA library:
>
> http://tukaani.org/lzma/
I went to the website to see which formats it supports, and was
surprised to read:
Users of LZMA Utils should move to XZ Utils. X
Shouldn't we just switch to xzutils instead?
> 2012-11-09 Alexander Larsson <alexl@redhat.com>
> Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * elfread.c (alloc_lzma, free_lzma): New functions.
> (gdb_lzma_allocator): New global.
> (struct lzma_stream): New.
> (lzma_open, lzma_pread, lzma_close, lzma_stat)
> (find_separate_debug_file_in_section): New functions.
> (elf_symfile_read): Call find_separate_debug_file_in_section if no
> other debuginfo is found.
Should we put the lzma-support code into its own file? I think it
would be cleaner, and also shows that this isn't really tied to ELF.
Perhaps there will be compressed sections in other file formats,
someday?
To avoid the #ifdef HAVE_LZMA, I might even provide two versions of the
file, one with the real implementation, and one with the phony one, and
have the configure choose which one to link in. This isn't what we've
been doing in the past (iconv, python), so to be taken with a grain of
salt. I think it'll make the code a little easier to navigate, however.
> * configure.ac: Check for lzma.
> * configure, config.in: Rebuild.
> * Makefile.in (LIBLZMA): New variable.
> (CLIBS): Include LIBLZMA.
> * NEWS: Mention mini debuginfo feature.
Otherwise, nicely clean and documented code!
--
Joel
next prev parent reply other threads:[~2012-11-09 18:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 17:33 Tom Tromey
2012-11-09 18:07 ` Eli Zaretskii
2012-11-09 18:13 ` Pedro Alves
2012-11-09 21:28 ` Tom Tromey
2012-11-13 12:56 ` Pedro Alves
2012-11-13 15:26 ` Pedro Alves
2012-11-13 18:32 ` Tom Tromey
2012-11-09 18:23 ` Joel Brobecker [this message]
2012-11-09 18:53 ` Pedro Alves
2012-11-09 19:13 ` Tom Tromey
2012-11-12 16:04 ` Tom Tromey
2012-11-12 17:04 ` Joel Brobecker
2012-11-12 18:24 ` Tom Tromey
2012-11-12 16:28 ` Tom Tromey
2012-11-13 18:36 ` Tom Tromey
2012-11-13 18:42 ` Eli Zaretskii
2012-11-13 19:12 ` Pedro Alves
2012-11-13 20:57 ` Tom Tromey
2012-11-14 16:13 ` Tom Tromey
2012-11-14 16:19 ` Pedro Alves
2012-11-14 16:59 ` Tom Tromey
2012-11-14 19:37 ` Doug Evans
2012-11-14 22:12 ` Joel Brobecker
2012-11-15 11:18 ` Pedro Alves
2012-11-16 19:51 ` Tom Tromey
2012-11-19 14:41 ` Pedro Alves
2012-11-26 19:21 ` Tom Tromey
2012-11-26 22:24 ` Andrew Pinski
2012-11-27 2:23 ` Tom Tromey
2012-11-29 19:19 ` Ulrich Weigand
2012-11-29 19:23 ` Tom Tromey
2012-11-29 19:33 ` Ulrich Weigand
2012-11-29 20:51 ` Tom Tromey
2012-11-30 14:05 ` Ulrich Weigand
2012-11-30 20:59 ` Tom Tromey
2012-12-05 17:09 ` Ulrich Weigand
2012-12-11 16:42 ` Yufeng Zhang
2012-11-16 20:04 ` Tom Tromey
2012-11-12 21:26 ` Doug Evans
2012-11-13 17:43 ` Tom Tromey
2012-11-13 15:44 ` Jan Kratochvil
2012-11-13 18:34 ` Tom Tromey
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=20121109182316.GQ5103@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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