From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Josh Matthews <josh@joshmatthews.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix darwin build error
Date: Mon, 22 Aug 2011 22:16:00 -0000 [thread overview]
Message-ID: <m3r54d3xfc.fsf@redhat.com> (raw)
In-Reply-To: <CAOvJiVUJT4Q5K0Od1MMci1grP-dND+9xRGy-FEXeVNPuRfv7iA@mail.gmail.com> (Josh Matthews's message of "Mon, 22 Aug 2011 16:19:25 -0400")
Hello Josh,
Josh Matthews <josh@joshmatthews.net> writes:
> I hope this is the right way to do this. GDB currently doesn't build
> on darwin, and this patch makes it do so.
Thanks for this. There are some nits, though.
Also, I don't see your name on the MAINTAINERS file. Do you have
copyright assignment from FSF? I don't know what's the procedure on
these cases... Maybe someone could commit the patch for you?
> gdb/
> 2011-08-22 Josh Matthews <josh@joshmatthews.net>
>
> Fix build error in darwin port.
You have to cite the file. Also, I believe you could be more
descriptive on the message. Something like:
* darwin-nat-info.c (darwin_debug_regions_recurse): Replacing
`uiout' by `current_uiout', fixing build error.
> --- a/gdb/darwin-nat-info.c
> +++ b/gdb/darwin-nat-info.c
> @@ -620,6 +620,7 @@ darwin_debug_regions_recurse (task_t task)
> kern_return_t kret;
> int ret;
> struct cleanup *table_chain;
> + struct ui_out* uiout = current_uiout;
The `*' shouldn't be placed there. This is the standard:
struct ui_out *uiout = current_uiout;
I think the current approach is to actually replace the occurrences of
`uiout' by `current_uiout', but I don't mind having a local `uiout'
variable.
Regards,
Sergio.
next prev parent reply other threads:[~2011-08-22 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 20:27 Josh Matthews
2011-08-22 22:16 ` Sergio Durigan Junior [this message]
2011-08-23 19:43 ` Jan Kratochvil
2011-08-23 20:47 ` Josh Matthews
2011-08-23 20:53 ` Keith Seitz
2011-08-23 20:57 ` Jan Kratochvil
2011-08-23 22:06 ` Sergio Durigan Junior
2012-01-31 22:00 [PATCH] Fix Darwin " Josh Matthews
2012-02-01 9:27 ` Tristan Gingold
2012-02-01 10:56 ` Joel Brobecker
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=m3r54d3xfc.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=josh@joshmatthews.net \
/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