Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Pierre Muller <muller@ics.u-strasbg.fr>
Subject: [patch] testsuite: gdb.pascal/gdb11492.exp ERROR: Process no longer  exists
Date: Mon, 26 Apr 2010 15:08:00 -0000	[thread overview]
Message-ID: <20100426150803.GA10434@host0.dyn.jankratochvil.net> (raw)

Hi,

getting
	Running ./gdb.pascal/gdb11492.exp ...
	ERROR: Process no longer exists
	ERROR: Process no longer exists
	ERROR: Process no longer exists
expect-5.43.0-19.fc12.x86_64
dejagnu-1.4.4-17.fc12.noarch

while I do not understand the reasons I am used to write testcases this way
and it also fixes this case.


Thanks,
Jan


gdb/testsuite/
2010-04-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.pascal/gdb11492.exp (print integer_array, print /d char_array)
	(print /x char_array): Escape curly brackets.

--- a/gdb/testsuite/gdb.pascal/gdb11492.exp
+++ b/gdb/testsuite/gdb.pascal/gdb11492.exp
@@ -46,12 +46,12 @@ if { [gdb_start_cmd] < 0 } {
 gdb_test "" ".* at .*${srcfile}.*" "start"
 gdb_test "continue" ""
 
-gdb_test "print integer_array" " = {50, 51, 52, 53, 54, 55, 56, 57}" 
+gdb_test "print integer_array" { = \{50, 51, 52, 53, 54, 55, 56, 57\}}
 gdb_test "print /s integer_array" " = '23456789'" 
 
 gdb_test "print char_array" " = '23456789'" 
-gdb_test "print /d char_array" " = {50, 51, 52, 53, 54, 55, 56, 57}" 
-gdb_test "print /x char_array" " = {0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39}" 
+gdb_test "print /d char_array" { = \{50, 51, 52, 53, 54, 55, 56, 57\}}
+gdb_test "print /x char_array" { = \{0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39\}}
 # Use next two times to avoid GPC line numbering problem
 gdb_test "next" ""
 gdb_test "next" ""


             reply	other threads:[~2010-04-26 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 15:08 Jan Kratochvil [this message]
2010-04-26 15:15 ` Pierre Muller
2010-04-26 15:50   ` 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=20100426150803.GA10434@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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