From: Luis Gustavo <luis_gustavo@mentor.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Stan Shebs <stanshebs@earthlink.net>
Subject: Re: [rfc target-side break conditions ] Testcase
Date: Fri, 24 Feb 2012 12:21:00 -0000 [thread overview]
Message-ID: <4F47808D.2050605@mentor.com> (raw)
In-Reply-To: <4F467B7F.6020500@redhat.com>
On 02/23/2012 03:46 PM, Pedro Alves wrote:
> On 02/22/2012 03:29 PM, Luis Gustavo wrote:
>
>> Fixed. Thanks for the input.
>
> Welcome.
>
>> I apologize for the poor expect hackery.
>
> No need for that. We all learn this stuff as we go.
>
> Okay, with ...
>
>> +gdb_test_multiple $test_target $test_target {
>> + -re $warning$gdb_prompt {
>
> -re "$warning$gdb_prompt $" {
>
> unless there's a special requirement to allow things after the prompt.
Not really. We just want to make sure target-side evaluation shows as
unsupported when doing native GDB debugging.
Thanks,
Luis
prev parent reply other threads:[~2012-02-24 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 23:17 Luis Gustavo
2012-02-14 14:29 ` Pedro Alves
2012-02-14 14:31 ` Pedro Alves
2012-02-22 15:33 ` Luis Gustavo
2012-02-23 17:51 ` Pedro Alves
2012-02-24 12:21 ` Luis Gustavo [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=4F47808D.2050605@mentor.com \
--to=luis_gustavo@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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