From: dje@google.com
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv2] gdb.base/valgrind-infcall.exp compat. with Ubuntu 10.04.4
Date: Tue, 07 Aug 2012 18:00:00 -0000 [thread overview]
Message-ID: <20513.22446.789388.617390@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <20120807113932.GA14482@host2.jankratochvil.net>
Jan Kratochvil writes:
> Does it work for you this way?
>
>
> Thanks,
> Jan
>
>
> gdb/testsuite/
> 2012-08-07 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.base/valgrind-infcall.exp (continue #$continue_count): Use
> global variable loop, not a 'break'. Add loop count limit to 100.
> Add new fail case for terminated vgdb.
Yes, thanks!
next prev parent reply other threads:[~2012-08-07 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 6:43 [patch] " Jan Kratochvil
2012-08-07 11:39 ` [patchv2] " Jan Kratochvil
2012-08-07 18:00 ` dje [this message]
2012-08-07 18:06 ` [commit+7.5] " Jan Kratochvil
2012-08-21 18:20 ` [patch] " Pedro Alves
2012-08-21 18:27 ` Jan Kratochvil
2012-08-21 18:41 ` Pedro Alves
2012-08-21 19:04 ` Jan Kratochvil
2012-08-21 20:01 ` Doug Evans
2012-08-24 14:28 ` Jan Kratochvil
2012-09-13 5:36 ` [commit+7.5] " Jan Kratochvil
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=20513.22446.789388.617390@ruffy2.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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