Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: handle "MiniDebuginfo" section
Date: Fri, 09 Nov 2012 18:13:00 -0000	[thread overview]
Message-ID: <509D47B5.6020302@redhat.com> (raw)
In-Reply-To: <87wqxuel5k.fsf@fleche.redhat.com>

There doesn't seem to be anything elf specific here.  It seems to me this
should work fine with any other container, such as coff/pe in coff/pe, for
example.  Can we move most of this code out of elf.c, or at least the
gross of it, even if elf_symfile_read remains unchanged?  I'd suggest
putting it in a new file.

> +#ifdef HAVE_LIBLZMA
> +
> +/* Custom lzma_allocator.alloc so they use the gdb ones.  */
> +
> +static void *
> +alloc_lzma (void *opaque, size_t nmemb, size_t size)
> +{
> +  return xmalloc (nmemb * size);
> +}
> +
> +/* Custom lzma_allocator.free so they use the gdb ones.  */
> +
> +static void
> +free_lzma (void *opaque, void *ptr)
> +{
> +  xfree (ptr);
> +}
> +
> +/* It cannot be const due to the lzma library function prototypes.  */
> +
> +static lzma_allocator gdb_lzma_allocator = { alloc_lzma, free_lzma, NULL};

Missing space after NULL.

(I find the "It" or "they" in these sentences confusing, but I don't
know whether that's just me and language barrier.)

> +/* Custom bfd_openr_iovec implementation to read compressed data from a
> +   section. This keeps only the last decompressed block in memory to

Missing space after '.'.

> diff --git a/gdb/testsuite/gdb.dwarf2/dw2-gnu-debugdata.exp b/gdb/testsuite/gdb.dwarf2/dw2-gnu-debugdata.exp
> new file mode 100644
> index 0000000..e384412
> --- /dev/null
> +++ b/gdb/testsuite/gdb.dwarf2/dw2-gnu-debugdata.exp

Seems like this won't work with remote hosts as is.  Can we make it use
"remote_file host delete", "remote_spawn host", etc.?  If not, perhaps just
bail early if [is_remote host].

-- 
Pedro Alves


  parent reply	other threads:[~2012-11-09 18:13 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 [this message]
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
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=509D47B5.6020302@redhat.com \
    --to=palves@redhat.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