Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] gdb.base/valgrind-infcall.exp compat. with Ubuntu 10.04.4
Date: Tue, 21 Aug 2012 18:27:00 -0000	[thread overview]
Message-ID: <20120821182731.GA2980@host2.jankratochvil.net> (raw)
In-Reply-To: <5033D14B.4090801@redhat.com>

On Tue, 21 Aug 2012 20:19:55 +0200, Pedro Alves wrote:
> On 08/07/2012 07:43 AM, Jan Kratochvil wrote:
> >  set continue_count 1
> > -while 1 {
> > +set loop 1
> > +while {$loop} {
> >      set test "continue #$continue_count"
> >      gdb_test_multiple "continue" "" {
> >  	-re "Invalid free\\(\\).*: main .*\r\n$gdb_prompt $" {
> >  	    pass $test
> > -	    break
> > +	    # In Ubuntu 10.04.4 environments 'break' does not work here.
> > +	    set loop 0
> >  	}
> 
> For archaeology, and for knowing when can we stop caring for this issue,
> it would be nice(r) IMO to know the tcl/expect version that triggered this issue.

This was "v1" patch, there is also "patchv2".

"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.


Thanks,
Jan


  reply	other threads:[~2012-08-21 18:27 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 [this message]
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=20120821182731.GA2980@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --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