From: Hui Zhu <teawater@gmail.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, lgustavo@codesourcery.com,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Support targets that know how to continue over breakpoints[4/4] -- testsuite
Date: Tue, 07 May 2013 02:46:00 -0000 [thread overview]
Message-ID: <CANFwon2bCw7AY6qhZpX4E1aYOTR202tMs4w+JMLArTSvZS0k4Q@mail.gmail.com> (raw)
In-Reply-To: <CANFwon0DCkOJ_uU1jpG3d88Hu=fbuBqmwZF8BU1gvePPexGvPA@mail.gmail.com>
Ping http://sourceware.org/ml/gdb-patches/2013-03/msg00066.html
Thanks,
Hui
On Sun, Mar 24, 2013 at 1:36 PM, Hui Zhu <teawater@gmail.com> wrote:
> Ping http://sourceware.org/ml/gdb-patches/2013-03/msg00057.html
>
> Thanks,
> Hui
>
> On Sun, Mar 3, 2013 at 10:18 AM, Hui Zhu <hui_zhu@mentor.com> wrote:
>> On 03/03/13 00:14, Hui Zhu wrote:
>>>
>>> Hello,
>>>
>>> This patch add a new test cob.exp use the "--cob" that add by prev patch
>>> test the continue over breakpoints function of GDB.
>>>
>>> Thanks,
>>> Hui
>>>
>>> 2013-03-03 Hui Zhu <hui_zhu@mentor.com>
>>>
>>> * gdb.server/Makefile.in (EXECUTABLES): Add cob.
>>> * gdb.server/cob.c: New file.
>>> * gdb.server/cob.exp: New file.
>>> * lib/gdbserver-support.exp (gdbserver_start): Add check for
>>> gdbserver_use_cob_p.
>>
>>
>> Because the option "--cob" is changed to "--continue-over-breakpoints". So
>> I post a new version for that change.
>>
>>
>> Thanks,
>> Hui
>>
>> 2013-03-03 Hui Zhu <hui_zhu@mentor.com>
>>
>> * gdb.server/Makefile.in (EXECUTABLES): Add cob.
>> * gdb.server/cob.c: New file.
>> * gdb.server/cob.exp: New file.
>> * lib/gdbserver-support.exp (gdbserver_start): Add check for
>> gdbserver_use_cob_p.
next prev parent reply other threads:[~2013-05-07 2:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 16:09 [PATCH] Support targets that know how to continue over breakpoints[1/4] -- GDB Hui Zhu
2013-03-02 16:11 ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Hui Zhu
2013-03-02 16:13 ` [PATCH] Support targets that know how to continue over breakpoints[3/4] -- gdbserver Hui Zhu
2013-03-02 16:14 ` [PATCH] Support targets that know how to continue over breakpoints[4/4] -- testsuite Hui Zhu
2013-03-03 2:18 ` Hui Zhu
2013-03-24 14:45 ` Hui Zhu
2013-05-07 2:46 ` Hui Zhu [this message]
2013-03-12 10:05 ` Hui Zhu
2013-03-02 16:20 ` [PATCH] Support targets that know how to continue over breakpoints[3/4] -- gdbserver Eli Zaretskii
2013-03-03 2:15 ` Hui Zhu
2013-03-24 14:10 ` Hui Zhu
2013-03-25 3:46 ` Eli Zaretskii
2013-03-25 8:06 ` Hui Zhu
2013-05-07 2:45 ` Hui Zhu
2013-03-12 10:05 ` Hui Zhu
2013-03-02 16:19 ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Eli Zaretskii
2013-03-03 2:06 ` Hui Zhu
2013-03-03 3:51 ` Eli Zaretskii
2013-03-03 3:58 ` Hui Zhu
2013-03-12 10:04 ` Hui Zhu
2013-05-07 2:37 ` Hui Zhu
2013-03-12 10:04 ` [PATCH] Support targets that know how to continue over breakpoints[1/4] -- GDB Hui Zhu
2013-03-24 12:33 ` Hui Zhu
2013-05-07 2:35 ` Hui Zhu
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=CANFwon2bCw7AY6qhZpX4E1aYOTR202tMs4w+JMLArTSvZS0k4Q@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=lgustavo@codesourcery.com \
--cc=palves@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