From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/Ada] Implement Ada tasking support
Date: Tue, 23 Sep 2008 19:22:00 -0000 [thread overview]
Message-ID: <m3wsh2zn27.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080922233209.GE24389@adacore.com> (Joel Brobecker's message of "Mon\, 22 Sep 2008 16\:32\:09 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Hi Joel. I have a couple "big" things to comment on about this patch,
plus a couple nit-picky things.
Joel> * info tasks:
Joel> * info task TASKNO:
Joel> * task [TASKNO]:
These names are all generic, but the feature is specific to Ada.
How about "info ada task" and "ada task" as the commands instead?
I am curious to know how this will interact with the "set" stuff
coming with Stan's multi-exec work.
Joel> I have omitted the part that allows you to restrict a breakpoint to
Joel> a given task ("break LINESPEC task TASKNO") for now, but will soon
Joel> start discussing this if this goes in.
How about using convenience functions instead of new syntax?
break LINESPEC if $current_ada_task() == 5
... unless, I suppose, there's some strong reason to prefer having
this information in the gdb internals.
Now for the nit picks. I only looked at this superficially, I'm
afraid.
Joel> +#define target_get_ada_task_ptid(lwp, tid) \
Joel> + (*current_target.to_get_ada_task_ptid) (lwp,tid)
Not sure if this kind of macro needs a comment?
Joel> +ptid_t
Joel> +default_get_ada_task_ptid (long lwp, long tid)
Comment needed.
Joel> +/* A short description corresponding to each possible task state. */
Joel> +static char *task_states[] = {
Joel> + "Unactivated",
I think these should be marked N_() and then run through gettext when
printing. Likewise for long_task_states.
Joel> +/* Set to 1 when the cached address of System.Tasking.Debug.Known_Tasks
Joel> + might be stale and so needs to be recomputed. */
Joel> +static int ada_tasks_check_symbol_table = 1;
For my own clarification -- is a blank line needed between the comment
and the definition here? Or is that only for functions? (If needed,
there are a few cases of this.)
Joel> +void
Joel> +iterate_over_live_ada_tasks (ada_task_list_iterator_ftype *iterator)
Comment needed.
Joel> +static ptid_t
Joel> +thread_db_get_ada_task_ptid (long lwp, long thread)
Likewise.
Tom
prev parent reply other threads:[~2008-09-23 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 23:33 Joel Brobecker
2008-09-23 3:20 ` Eli Zaretskii
2008-09-23 15:07 ` Joel Brobecker
2008-09-23 18:06 ` Eli Zaretskii
2008-09-23 18:30 ` Joel Brobecker
2008-09-23 19:17 ` Eli Zaretskii
2008-09-23 19:00 ` Tom Tromey
2008-09-23 18:24 ` Eli Zaretskii
2008-09-23 19:22 ` Tom Tromey [this message]
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=m3wsh2zn27.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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