Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: palves@redhat.com (Pedro Alves), dje@google.com (Doug Evans),
	       gdb-patches@sourceware.org
Subject: Re: RFA: handle "MiniDebuginfo" section
Date: Thu, 29 Nov 2012 19:23:00 -0000	[thread overview]
Message-ID: <87fw3s5i3x.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201211291919.qATJJ379024978@d06av02.portsmouth.uk.ibm.com>	(Ulrich Weigand's message of "Thu, 29 Nov 2012 20:19:03 +0100 (CET)")

>>>>> "Ulrich" == Ulrich Weigand <uweigand@de.ibm.com> writes:

Ulrich> ERROR: (DejaGnu) proc "lassign {nm {-D
Ulrich> /home/uweigand/fsf/gdb-head-build/gdb/testsuite/gdb.base/gnu-debugdata
Ulrich> --format=posix --defined-only}} program arguments input output" does
Ulrich> not exist.

Ulrich> I'm not really familiar enough with DejaGnu/Tcl to quite understand
Ulrich> what's going on here ...    Any thoughts?

I think lassign was added in Tcl 8.5.
You must be running an older version.

Can you try the appended?

Tom

diff --git a/gdb/testsuite/gdb.base/gnu-debugdata.exp b/gdb/testsuite/gdb.base/gnu-debugdata.exp
index f876309..1429a39 100644
--- a/gdb/testsuite/gdb.base/gnu-debugdata.exp
+++ b/gdb/testsuite/gdb.base/gnu-debugdata.exp
@@ -33,7 +33,8 @@ proc run {test program args} {
     }
     set result [eval remote_exec host [list $program] $args]
     verbose "result is $result"
-    lassign $result status output
+    set status [lindex $result 0]
+    set output [lindex $result 1]
     if {$status == 0} {
  	pass $test
  	return 0
@@ -58,7 +59,11 @@ proc pipeline {test args} {
     set input_file {}
     foreach arglist $args {
 	verbose "raw args are $arglist"
-	lassign $arglist program arguments input output
+
+	set program [lindex $arglist 0]
+	set arguments [lindex $arglist 1]
+	set input [lindex $arglist 2]
+	set output [lindex $arglist 3]
 
 	if {$input == ""} {
 	    set input $input_file


  reply	other threads:[~2012-11-29 19:23 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 17:33 Tom Tromey
2012-11-09 18:07 ` Eli Zaretskii
2012-11-09 18:13 ` Pedro Alves
2012-11-09 21:28   ` Tom Tromey
2012-11-13 12:56     ` Pedro Alves
2012-11-13 15:26       ` Pedro Alves
2012-11-13 18:32       ` Tom Tromey
2012-11-09 18:23 ` Joel Brobecker
2012-11-09 18:53   ` Pedro Alves
2012-11-09 19:13   ` Tom Tromey
2012-11-12 16:04   ` Tom Tromey
2012-11-12 17:04     ` Joel Brobecker
2012-11-12 18:24       ` Tom Tromey
2012-11-12 16:28 ` Tom Tromey
2012-11-13 18:36   ` Tom Tromey
2012-11-13 18:42     ` Eli Zaretskii
2012-11-13 19:12     ` Pedro Alves
2012-11-13 20:57       ` Tom Tromey
2012-11-14 16:13         ` Tom Tromey
2012-11-14 16:19           ` Pedro Alves
2012-11-14 16:59             ` Tom Tromey
2012-11-14 19:37           ` Doug Evans
2012-11-14 22:12             ` Joel Brobecker
2012-11-15 11:18             ` Pedro Alves
2012-11-16 19:51               ` Tom Tromey
2012-11-19 14:41                 ` Pedro Alves
2012-11-26 19:21                   ` Tom Tromey
2012-11-26 22:24                     ` Andrew Pinski
2012-11-27  2:23                       ` Tom Tromey
2012-11-29 19:19                     ` Ulrich Weigand
2012-11-29 19:23                       ` Tom Tromey [this message]
2012-11-29 19:33                         ` Ulrich Weigand
2012-11-29 20:51                           ` Tom Tromey
2012-11-30 14:05                             ` Ulrich Weigand
2012-11-30 20:59                               ` Tom Tromey
2012-12-05 17:09                                 ` Ulrich Weigand
2012-12-11 16:42                     ` Yufeng Zhang
2012-11-16 20:04             ` Tom Tromey
2012-11-12 21:26 ` Doug Evans
2012-11-13 17:43   ` Tom Tromey
2012-11-13 15:44 ` Jan Kratochvil
2012-11-13 18:34   ` Tom Tromey

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=87fw3s5i3x.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=uweigand@de.ibm.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