From: Samuel Bronson <naesten@gmail.com>
To: tromey@redhat.com
Cc: Samuel Bronson <naesten@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Add an undwinder_name field to "struct frame_unwind" for use by "info frame".
Date: Tue, 09 Jun 2009 00:24:00 -0000 [thread overview]
Message-ID: <871vpudzkd.wl%naesten@gmail.com> (raw)
In-Reply-To: <m37hzrwtgi.fsf@fleche.redhat.com>
At Thu, 04 Jun 2009 15:59:57 -0600,
Tom Tromey wrote:
>
> >>>>> "Samuel" == Samuel Bronson <naesten@gmail.com> writes:
>
> Samuel> Have "info frame" display this field when present.
> Samuel> Fill in the field for unwinders (besides the sentinel) which are
> Samuel> normally built on i386 Linux.
>
> Funnily enough, I wanted this yesterday :)
>
> This mostly looks ok. It needs a ChangeLog entry. And I have some
> formatting nits...
Hmm. How is that different from the thing above the patch (aka "commit
message")?
> Samuel> +const char *get_frame_unwinder_name (struct frame_info *frame)
>
> Newline after the first "*".
Ah.
> Samuel> + unwinder = get_frame_unwinder_name(fi);
>
> Space before the open paren.
Yeah, I've noticed that you always put those in and have been doing so
myself more recently.
> Also, do you have copyright assignment papers in place? Those are a
> prerequisite for us to accept a non-trivial patch.
Ah, no, not yet. I assume this doesn't qualify? I'd be fairly happy
to do so, my concerns at this point being:
a) what if I write some fairly generic code and end up wanting to BSD it?
b) how do I know you aren't going to add front- or back-cover texts
or invariant sections to the manual?
next prev parent reply other threads:[~2009-06-09 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 23:09 Samuel Bronson
2009-05-29 23:10 ` [PATCH 2/2] Add "set/show debug unwinder" prefix commands Samuel Bronson
2009-05-30 6:57 ` Eli Zaretskii
2009-05-30 19:25 ` Doug Evans
2009-05-31 15:50 ` Samuel Bronson
2009-06-04 22:05 ` Tom Tromey
2009-06-09 0:49 ` Samuel Bronson
2009-06-09 19:44 ` Tom Tromey
2009-06-04 22:00 ` [PATCH 1/2] Add an undwinder_name field to "struct frame_unwind" for use by "info frame" Tom Tromey
2009-06-09 0:24 ` Samuel Bronson [this message]
2009-06-09 19:41 ` 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=871vpudzkd.wl%naesten@gmail.com \
--to=naesten@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