From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, saugustine@google.com, ccoutant@google.com
Subject: Re: [patch] DWP V2 support
Date: Mon, 30 Sep 2013 19:41:00 -0000 [thread overview]
Message-ID: <87a9iu9jy0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <yjt2ob7danre.fsf@ruffy.mtv.corp.google.com> (Doug Evans's message of "Fri, 27 Sep 2013 15:44:05 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I plan to leave this for a few days for comments, and then commit.
Doug> +/* Possible section ids for version 2 DWP files.
Doug> + These values are specified by the DWP spec. */
Doug> +
Doug> +enum dwp_v2_section_ids
Doug> +{
Doug> + DWP_V2_DW_SECT_MIN = 1,
I suspect this is better placed in include/dwarf2.h.
Presumably some other tool needs this same enum.
Tom
next prev parent reply other threads:[~2013-09-30 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 22:44 Doug Evans
2013-09-30 19:41 ` Tom Tromey [this message]
2013-09-30 19:45 ` Cary Coutant
2013-10-01 15:08 ` Tom Tromey
2013-10-05 2:14 ` Doug Evans
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=87a9iu9jy0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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).