Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Victor Leschuk <vleschuk@accesssoftek.com>
Subject: Re: [PATCH 5/8] DWARF-5 basic functionality
Date: Sun, 19 Feb 2017 21:26:00 -0000	[thread overview]
Message-ID: <20170219212630.GC1291@host1.jankratochvil.net> (raw)
In-Reply-To: <18b01458-037f-d871-8195-19731a35d38e@redhat.com>

On Fri, 17 Feb 2017 12:41:22 +0100, Pedro Alves wrote:
> > +ULONGEST gdb_read_unsigned_leb128 (bfd *, const gdb_byte *, unsigned int *);
> 
> Not needed anymore.

Yes, dropped.


> > +#include "libbfd.h"
> 
> We've determined this is an internal bfd header.
> Do we need this?

No, a mistake, dropped.


> > +/* Expected enum dwarf_unit_type for read_comp_unit_head.  */
> > +enum class RCUH_Kind { COMPILE, TYPE };
> 
> RCUH_Kind -> rcuh_kind.  We only use uppercase type names
> in template type parameter names.

Done.


> > -/* Call CALLBACK from DW_AT_ranges attribute value OFFSET.
> > +/* Call CALLBACK from DW_AT_ranges attribute value OFFSET
> > +   reading .debug_rnglists.
> > +   Return 1 if the attributes are present and valid, otherwise, return 0.  */
> > +
> > +static int
> > +dwarf2_rnglists_process (unsigned offset, struct dwarf2_cu *cu,
> 
> bool/true/false?

It is just a variant of dwarf2_ranges_process which still does use int from
the C days of GDB.  Its return value is also passed as a return value of
dwarf2_ranges_process.  Using bool here would need to refactor
dwarf2_ranges_process first.  And then one can rather refactor it all to
a virtual class and after more refactoring to a different debugger.

So I have kept it as it was.  Otherwise specify which level of refactorization
do you wish.


> > +			 std::function<void (CORE_ADDR range_beginning,
> > +					     CORE_ADDR range_end)> callback)
> 
> Same comment about std::function.  (and I had forgotten to suggest
> that callback should probably be a universal reference / "&&callback").

That is OK, I have already noticed you had studied a lot of C++ schoolbooks
before you permitted GDB to use C++.


Jan


  reply	other threads:[~2017-02-19 21:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 20:23 [PATCH 1/8] Rename read_unsigned_leb128 to gdb_read_unsigned_leb128 Jan Kratochvil
2017-02-12 20:23 ` [PATCH 7/8] DWARF-5: Macros Jan Kratochvil
2017-02-17 11:59   ` Pedro Alves
2017-02-12 20:23 ` [PATCH 6/8] DWARF-5: call sites Jan Kratochvil
2017-02-12 20:41   ` Eli Zaretskii
2017-02-17 11:57   ` Pedro Alves
2017-02-19 21:26     ` Jan Kratochvil
2017-02-12 20:23 ` [PATCH 8/8] DWARF-5: DW_FORM_data16 Jan Kratochvil
2017-02-17 12:09   ` Pedro Alves
2017-02-19 21:26     ` Jan Kratochvil
2017-02-20 11:44       ` Pedro Alves
2017-02-17 12:24   ` Pedro Alves
2017-02-12 20:23 ` [PATCH 3/8] Code cleanup: Split dwarf2_ranges_read to a callback Jan Kratochvil
2017-02-17  1:19   ` Pedro Alves
2017-02-19 21:26     ` Jan Kratochvil
2017-02-20 11:11       ` Pedro Alves
2017-02-12 20:23 ` [PATCH 5/8] DWARF-5 basic functionality Jan Kratochvil
2017-02-17 11:41   ` Pedro Alves
2017-02-19 21:26     ` Jan Kratochvil [this message]
     [not found]       ` <e23e71b0-3cf7-ca57-c4a7-932d4d2be6a3@redhat.com>
2017-02-20 19:52         ` Jan Kratochvil
2017-02-20 20:07           ` [commit] " Jan Kratochvil
2017-02-12 20:23 ` [PATCH 2/8] Code cleanup: Split create_debug_types_hash_table Jan Kratochvil
2017-02-16 19:33   ` Pedro Alves
2017-02-12 20:23 ` [PATCH 4/8] Code cleanup: Refactor abbrev_table_read_table cycle Jan Kratochvil
2017-02-17  1:21   ` Pedro Alves
2017-02-16 15:23 ` [PATCH 1/8] Rename read_unsigned_leb128 to gdb_read_unsigned_leb128 Pedro Alves
2017-02-16 19:40   ` Jan Kratochvil
2017-02-16 20:01     ` Pedro Alves
2017-02-16 22:54       ` Pedro Alves
2017-02-17  1:28         ` Pedro Alves
2017-02-19 21:25         ` Jan Kratochvil

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=20170219212630.GC1291@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=vleschuk@accesssoftek.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