public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: archer@sourceware.org
Subject: [python] [commit] Remove python-support.exp
Date: Mon, 10 Jan 2011 12:41:00 -0000	[thread overview]
Message-ID: <m3tyhhaq36.fsf@redhat.com> (raw)


I have removed python-support.exp.  This file is no longer
used. Upstream has a gdb-python.exp library where these functions have
been exported.

I  also had to remove a load-lib reference from gdb.exp.

Cheers,

Phil
--

commit a92f03033f8189004371649d4938378c0756852c
Author: Phil Muldoon <pmuldoon@redhat.com>
Date:   Mon Jan 10 12:34:29 2011 +0000

    Do not load python-support.exp

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 62466f8..5a3f1fc 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -28,7 +28,6 @@ if {$tool == ""} {
 }
 
 load_lib libgloss.exp
-load_lib python-support.exp
 
 global GDB
 

commit fe209e2360570eedf77b88a3614a2d85557921d9
Author: Phil Muldoon <pmuldoon@redhat.com>
Date:   Mon Jan 10 12:32:52 2011 +0000

    Remove python-support.exp.  Do not load it in gdb.exp.

diff --git a/gdb/testsuite/lib/python-support.exp b/gdb/testsuite/lib/python-support.exp
deleted file mode 100644
index b8e9836..0000000
--- a/gdb/testsuite/lib/python-support.exp
+++ /dev/null
@@ -1,53 +0,0 @@
-global python_supported_saved
-
-# Return 1 if Python scripting is supported in GDB, 0 if not.
-proc python_supported { } {
-  global gdb_prompt
-  global python_supported_saved
-
-  if [info exists python_supported_saved] {
-      verbose "python_supported:  returning saved $python_supported_saved" 2
-      return $python_supported_saved
-  }
-
-  gdb_test_multiple "python print 'hello, world!'" "verify python support" {
-    -re "not supported.*$gdb_prompt $"	{
-      return [set python_supported_saved 0]
-    }
-    -re "$gdb_prompt $"	{
-      return [set python_supported_saved 1]
-    }
-  }
-
-  return [set python_supported_saved 0]
-}
-
-# Run a command in GDB, and report a failure if a Python exception is thrown.
-# If report_pass is true, report a pass if no exception is thrown.
-proc gdb_py_test_silent_cmd {cmd name report_pass} {
-  global gdb_prompt
-
-  gdb_test_multiple $cmd $name {
-      -re "Traceback.*$gdb_prompt $"  { fail $name }
-      -re "$gdb_prompt $"	      { if $report_pass { pass $name } }
-  }
-}
-
-# Usage: gdb_py_test_multiple NAME INPUT RESULT {INPUT RESULT}...
-# Run a test named NAME, consisting of multiple lines of input.
-# After each input line INPUT, search for result line RESULT.
-# Succeed if all results are seen; fail otherwise.
-proc gdb_py_test_multiple {name args} {
-    global gdb_prompt
-
-    foreach {input result} $args {
-	if {[gdb_test_multiple $input "$name - $input" {
-	    -re "\[\r\n\]*($result)\[\r\n\]+($gdb_prompt | *>)$" {
-		pass "$name - $input"
-	    }
-	}]} {
-	    return 1
-	}
-    }
-    return 0
-}

                 reply	other threads:[~2011-01-10 12:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3tyhhaq36.fsf@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=archer@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).