From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Add task-specific breakpoint capability...
Date: Wed, 25 Mar 2009 21:22:00 -0000 [thread overview]
Message-ID: <uy6utmkix.fsf@gnu.org> (raw)
In-Reply-To: <20090325195633.GC9472@adacore.com>
> Date: Wed, 25 Mar 2009 12:56:33 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> OK, here is a new version of the patch. Hopefully, everything that we
> discussed earlier should be incorporated, and I also tried to fix
> a few tab/spaces issues (my favorite :). I'm also adding a testcase.
Thanks.
> gdb/:
> 2009-03-25 Joel Brobecker <brobecker@adacore.com>
>
> Provide support for (Ada) task-specific breakpoints.
>
> * ada-lang.h (ada_get_task_number): Add declaration.
> (breakpoint_ada_task_match): Delete declaration.
> * ada-tasks.c (ada_get_task_number): Make non-static.
> * breakpoint.h (struct breakpoint): Add field "task".
> * breakpoint.c (print_one_breakpoint_location): Add handling of
> task-specific breakpoints.
> (create_breakpoint, create_breakpoints, find_condition_and_thread):
> New parameter "task".
> (break_command_really): Update calls to find_condition_and_thread
> and create_breakpoints.
> (breakpoint_re_set_one): Update call to find_condition_and_thread.
> Set b->task.
>
> gdb/testsuite/:
> 2009-03-25 Joel Brobecker <brobecker@adacore.com>
>
> * gdb.ada/tasks: New testcase.
Hmm?... no documentation?
next prev parent reply other threads:[~2009-03-25 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 21:27 Joel Brobecker
2009-03-24 23:55 ` Tom Tromey
2009-03-25 16:27 ` Joel Brobecker
2009-03-25 16:34 ` Joel Brobecker
2009-03-25 16:39 ` Tom Tromey
2009-03-25 17:49 ` Joel Brobecker
2009-03-25 19:58 ` Joel Brobecker
2009-03-25 21:22 ` Eli Zaretskii [this message]
2009-03-31 16:55 ` 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=uy6utmkix.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.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