From: Nick Roberts <nickrob@snap.net.nz>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: linux native async mode support
Date: Tue, 18 Mar 2008 02:47:00 -0000 [thread overview]
Message-ID: <18399.11554.144087.991511@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200803171605.24276.pedro@codesourcery.com>
I've really gone through your patch to try to understand it, not review it
but you might as well have my thoughts.
> * linux-nat.h (re_check_for_thread_db): Declare.
recheck_for_thread_db (assuming it means "check again").
The word "re" on it's own is an abbreviation for "regarding" and
in GDB it's generally used for "regular expression".
>...
> +static void
> +clear_waitpid_queue (void)
> +{
> + struct waitpid_result *event = waitpid_queue;
> + while (event)
> + {
> + struct waitpid_result *next = event->next;
> + xfree (event);
> + event = next;
> + }
> + waitpid_queue = NULL;
> +}
struct waitpid_result *next, *event = waitpid_queue;
while (event)
{
next = event->next;
xfree (event);
event = next;
I guess the compiler will optimise it anyway but shouldn't
the declaration be outside the loop?
>...
> +/* Disable async mode. */
> +
> +static void
> +linux_nat_disable_async (void)
and
> +/* Enable async mode. */
> +
> +static void
> +linux_nat_enable_async (void)
Previously you've added linux_nat_async_events (int enable). So should
this be:
linux_nat_toggle_async (int enable)
for consistency? (or linux_nat_async_events -> linux_nat_async_disable_events
linux_nat_async_enable_events)
As a rule what does GDB do elsewhere in these situations?
>...
> + add_setshow_zinteger_cmd ("lin-lwp-async", no_class,
> + &debug_linux_nat_async, _("\
> +Set debugging of GNU/Linux async lwp module."), _("\
> +Show debugging of GNU/Linux async lwp module."), _("\
> +Enables printf debugging output."),
> + NULL,
> + show_debug_linux_nat_async,
> + &setdebuglist, &showdebuglist);
add_setshow_boolean_cmd ("lin-lwp-async", class_maintenance,
I guess you copied from "lin-lwp" but I think this should be
boolean too (only a few currently are: timestamp and xml)
The other "set debug" commands are also in class_maintenance, although
I'm not sure what effect that has here.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-03-18 2:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 8:11 Pedro Alves
2008-03-14 21:17 ` Daniel Jacobowitz
2008-03-17 16:05 ` Pedro Alves
2008-03-17 22:05 ` Daniel Jacobowitz
2008-03-18 23:27 ` Pedro Alves
2008-03-18 23:58 ` Daniel Jacobowitz
2008-03-21 15:55 ` Daniel Jacobowitz
2008-03-21 17:19 ` Pedro Alves
2008-03-28 14:48 ` Maciej W. Rozycki
2008-03-28 16:07 ` Pedro Alves
2008-03-28 16:13 ` Daniel Jacobowitz
2008-03-28 16:40 ` Pedro Alves
2008-03-18 0:06 ` Nick Roberts
2008-03-18 23:28 ` Pedro Alves
2008-03-19 3:59 ` Nick Roberts
2008-03-19 16:25 ` Luis Machado
2008-03-19 23:19 ` Pedro Alves
2008-03-19 23:26 ` Pedro Alves
2008-03-20 1:58 ` Nick Roberts
2008-03-21 15:47 ` Daniel Jacobowitz
2008-03-21 15:49 ` Daniel Jacobowitz
2008-03-21 23:02 ` Nick Roberts
2008-03-22 1:25 ` Daniel Jacobowitz
2008-03-22 22:06 ` Nick Roberts
2008-04-01 14:00 ` Daniel Jacobowitz
2008-04-01 15:17 ` Vladimir Prus
2008-04-01 20:09 ` Nick Roberts
2008-04-04 12:34 ` Vladimir Prus
2008-04-05 17:20 ` Nick Roberts
2008-04-05 22:07 ` Vladimir Prus
2008-04-07 0:06 ` Nick Roberts
2008-04-07 2:33 ` Nick Roberts
2008-03-18 2:47 ` Nick Roberts [this message]
2008-03-14 23:10 ` Nick Roberts
2008-03-15 1:58 ` Pedro Alves
2008-03-15 3:11 ` Daniel Jacobowitz
2008-03-17 23:41 ` Nick Roberts
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=18399.11554.144087.991511@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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