From: Hui Zhu <teawater@gmail.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, Yao Qi <Yao_Qi@mentor.com>,
Stan Shebs <stan_shebs@mentor.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Autoload-breakpoints without report-async
Date: Tue, 15 May 2012 11:29:00 -0000 [thread overview]
Message-ID: <CANFwon0fFEk=K6iQG5wsm+tYJMLFAba-jYKr-V7jm__dxb9pTA@mail.gmail.com> (raw)
In-Reply-To: <4FA2B434.60706@mentor.com>
Ping.
Thanks,
Hui
On Fri, May 4, 2012 at 12:37 AM, Hui Zhu <hui_zhu@mentor.com> wrote:
> Hi guys,
>
> According to the mail form Yao. I thought make the autoload-breakpoints and
> report-async function together make it too hard to review. So I move the
> function that depend on the report-async to be a series of separate patches
> after report-async.
> Then the other patches of autoload-breakpoints can be reveiw separate from
> report-async.
>
> Thanks,
> Hui
>
> 2012-05-04 Hui Zhu <hui_zhu@mentor.com>
>
> * breakpoint.c (hex2bin, unpack_varlen_hex): New extern.
> (autoload_breakpoints_query, autoload_breakpoints_merge,
> autoload_breakpoints_gdb, autoload_breakpoints_stub,
> autoload_breakpoints_enums, this_ubpcmd): New variable.
> (breakpoint_get_commands): New function.
> (print_one_breakpoint): Add out for b->autoload_id.
> (init_raw_breakpoint_without_location): Add init for autoload_id
> and autoload_inserted.
> (autoload_breakpoints_get_id, uploaded_bp_commands_clean,
> uploaded_bp_commands_add, handle_autoload_breakpoint_cmd,
> parse_autoload_breakpoint_definition,
> handle_autoload_breakpoint_cmd_to_breakpoints,
> parse_autoload_breakpoint_definition_to_breakpoints,
> clean_upload_autoload_breakpoints,
> show_upload_autoload_breakpoints,
> read_autoload_breakpoints_action,
> merge_uploaded_autoload_breakpoints, autoload_breakpoints_reset,
> autoload_breakpoints_clean,
> autoload_breakpoints_number): New function.
> (initialize_breakpoint_ops): add command "autoload".
> * breakpoint.h (breakpoint): Add autoload_id and autoload_inserted.
> (uploaded_bpcmd, uploaded_bp): New struct.
> (autoload_breakpoints_query, autoload_breakpoints_merge,
> autoload_breakpoints_gdb, autoload_breakpoints_stub,
> autoload_breakpoints_mode, breakpoint_get_commands,
> autoload_breakpoints_reset, autoload_breakpoints_clean,
> autoload_breakpoints_number, parse_autoload_breakpoint_definition,
> parse_autoload_breakpoint_definition_to_breakpoints,
> clean_upload_autoload_breakpoints, show_upload_autoload_breakpoints,
> merge_uploaded_autoload_breakpoints): New extern.
> * remote.c (PACKET_AutoloadBreakpoints): New enum.
> (remote_start_remote): Check PACKET_AutoloadBreakpoints,
> if need call autoload-breakpoints functions.
> (remote_pr): Add PACKET_AutoloadBreakpoints.
> (remote_reportasync_handler): Add handle for "QBDP".
> (remote_upload_autoload_breakpoints,
> remote_download_autoload_breakpoints): New functions.
>
> 2012-05-04 Hui Zhu <hui_zhu@mentor.com>
>
> * gdb.texinfo (Setting Breakpoints): Add set breakpoint autoload.
> (Remote Serial Protocol): Add Autoload-breakpoints Format.
prev parent reply other threads:[~2012-05-15 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 16:37 Hui Zhu
2012-05-03 17:03 ` Eli Zaretskii
2012-05-04 1:00 ` Hui Zhu
2012-05-04 7:02 ` Eli Zaretskii
2012-05-06 1:53 ` Hui Zhu
2012-05-07 19:40 ` Eli Zaretskii
2012-05-15 11:29 ` Hui Zhu [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='CANFwon0fFEk=K6iQG5wsm+tYJMLFAba-jYKr-V7jm__dxb9pTA@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=Yao_Qi@mentor.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=stan_shebs@mentor.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