Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] gdb.base/valgrind-infcall.exp compat. with Ubuntu 10.04.4
Date: Tue, 21 Aug 2012 20:01:00 -0000	[thread overview]
Message-ID: <CADPb22Ry8_KvsE0o0XAMgpoA5DQ3VM3xr0xx+M_1WpvL=Mccrg@mail.gmail.com> (raw)
In-Reply-To: <20120821190428.GA3994@host2.jankratochvil.net>

On Tue, Aug 21, 2012 at 12:04 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Tue, 21 Aug 2012 20:41:18 +0200, Pedro Alves wrote:
>> On 08/21/2012 07:27 PM, Jan Kratochvil wrote:
>> > "patchv2" fixes also the case of "The program is not being run".  I believe
>> > the Doug's problem was due to it and not due to the "break" statement.  But
>> > I failed to reproduce the Doug's problem so I left it as is.
>> >
>> > The comment just states the bugreport, nothing more.
>>
>> Understood.  The comment is still there on v2, so the point still stands
>> though.
>
> Unless Doug speaks up with a verification I will just remove the comment.

I'd say keep the comment in some form.

The tcl/expect I've been using is
$ expect -v
expect version 5.44.1.14
$ ldd /usr/bin/expect | grep tcl
        libtcl8.5.so.0 => /usr/lib/libtcl8.5.so.0 (0x00007ff9bac15000)


  reply	other threads:[~2012-08-21 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  6:43 Jan Kratochvil
2012-08-07 11:39 ` [patchv2] " Jan Kratochvil
2012-08-07 18:00   ` dje
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 [this message]
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='CADPb22Ry8_KvsE0o0XAMgpoA5DQ3VM3xr0xx+M_1WpvL=Mccrg@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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