From: Doug Evans <xdje42@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@gmail.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH] include/gdb/section-scripts.h: New file.
Date: Mon, 02 Dec 2013 17:01:00 -0000 [thread overview]
Message-ID: <CAP9bCMT2s-BMsyafMiZrNmhkAqTowmfjkHfJAQMEQpRQOhqzag@mail.gmail.com> (raw)
In-Reply-To: <87eh5vwaa3.fsf@fleche.redhat.com>
On Mon, Dec 2, 2013 at 7:19 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@gmail.com> writes:
>
> Doug> This patch creates a file to use when adding values to
> Doug> .debug_gdb_scripts.
>
> I don't see why this needs to go in include.
So you would have code that puts contents in this section using magic numbers?
Eh? This doesn't make any sense. Why does dwarf2.def exist (for example) ?
[The dwarf format is far more complicated, obvously. But I didn't
know there was
a threshold of magic numbers was required before a header was allowed.]
> I think it would be more helpful to document the format of this section
> in the manual.
Documentation can always be improved, but there is something there already.
I do need to spiff it up, that's coming ...
> Doug> +/* Native GDB scripts are not currently supported in .debug_gdb_scripts,
> Doug> + but we reserve a value for it. */
> Doug> +/*#define SECTION_SCRIPT_ID_GDB_FILE 2*/
>
> There's no need either to reserve a value or to add commented out code.
I'm curious how I would apply this rule in general.
next prev parent reply other threads:[~2013-12-02 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 19:59 Doug Evans
2013-12-02 15:19 ` Tom Tromey
2013-12-02 17:01 ` Doug Evans [this message]
2013-12-03 16:17 ` Doug Evans
2013-12-05 21:07 ` Tom Tromey
2013-12-07 20:56 ` 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=CAP9bCMT2s-BMsyafMiZrNmhkAqTowmfjkHfJAQMEQpRQOhqzag@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=binutils@sourceware.org \
--cc=dje@gmail.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