From: Pedro Alves <palves@redhat.com>
To: "Gustavo, Luis" <luis_gustavo@mentor.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb-patches@sourceware.org
Subject: Re: [rfc target-side break conditions 5/5 v2] GDBServer-side changes
Date: Fri, 24 Feb 2012 13:01:00 -0000 [thread overview]
Message-ID: <4F4789FE.7080004@redhat.com> (raw)
In-Reply-To: <4F478803.30505@mentor.com>
On 02/24/2012 12:52 PM, Luis Gustavo wrote:
>
> 2012-02-24 Luis Machado <lgustavo@codesourcery>
>
> gdbserver/
> * server.c (handle_query): Advertise support for target-side
> breakpoint condition evaluation.
> (process_point_options): New function.
> (process_serial_event): When inserting a breakpoint, check for
> a target-side condition that should be evaluated.
>
> * mem-break.c: Include regcache.h and ax.h.
> (point_cond_list_t): New data structure.
> (breakpoint) <cond_list>: New field.
> (find_gdb_breakpoint_at): Make non-static.
> (delete_gdb_breakpoint_at): Clear any target-side
> conditions.
> (clear_gdb_breakpoint_conditions): New function.
> (add_condition_to_breakpoint): Likewise.
> (add_breakpoint_condition): Likewise.
> (gdb_condition_true_at_breakpoint): Likewise.
> (gdb_breakpoint_here): Return result directly instead
> of going through a local variable.
>
> * mem-break.h (find_gdb_breakpoint_at): New prototype.
> (clear_gdb_breakpoint_conditions): Likewise.
> (add_breakpoint_condition): Likewise.
> (gdb_condition_true_at_breakpoint): Likewise.
>
> * linux-low.c (linux_wait_1): Evaluate target-side breakpoint condition.
> (need_step_over_p): Take target-side breakpoint condition into
> consideration.
Okay.
--
Pedro Alves
prev parent reply other threads:[~2012-02-24 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 20:34 Luis Gustavo
2012-02-07 22:14 ` Stan Shebs
2012-02-08 23:14 ` Luis Gustavo
2012-02-09 12:33 ` Pedro Alves
2012-02-22 15:25 ` Luis Gustavo
2012-02-23 17:25 ` Pedro Alves
2012-02-24 12:19 ` Luis Gustavo
2012-02-24 12:52 ` Pedro Alves
2012-02-24 12:59 ` Luis Gustavo
2012-02-24 13:01 ` Pedro Alves [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=4F4789FE.7080004@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis_gustavo@mentor.com \
--cc=stanshebs@earthlink.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