public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/12238] New: while executing bad option "add": must be variable, vdelete, or vinfo
Date: Fri, 19 Nov 2010 22:40:00 -0000	[thread overview]
Message-ID: <bug-12238-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12238

           Summary: while executing bad option "add": must be variable,
                    vdelete, or vinfo
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: danglin@gcc.gnu.org


Testsuite problem:

Test Run By dave on Thu Nov 18 19:23:51 2010
Native configuration is hppa2.0w-hp-hpux11.11

                === gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /opt/gnu/share/dejagnu/baseboards/unix.exp as board description file for
t
arget.
Using /opt/gnu/share/dejagnu/config/unix.exp as generic interface file for
targe
t.
Using ../../../src/gdb/testsuite/config/unix.exp as tool-and-target-specific
int
erface file.
Running ../../../src/gdb/testsuite/gdb.xml/tdesc-arch.exp ...
bad option "add": must be variable, vdelete, or vinfo
    while executing
"trace add variable "$banned_var" write error"
    (procedure "gdb_init" line 15)
    invoked from within
"${tool}_init $test_file_name"
    (procedure "runtest" line 19)
    invoked from within
"runtest $test_name"
    ("foreach" body line 42)
    invoked from within
"foreach test_name [lsort [find ${dir} *.exp]] {
                        if { ${test_name} == "" } {
                            continue
                        }
                        # Ignore this one if asked to.
                        if { ${ignore..."
    ("foreach" body line 54)
    invoked from within
"foreach dir "${test_top_dirs}" {
                if { ${dir} != ${srcdir} } {
                    # Ignore this directory if is a directory to be
                    # ignored.
                    if {[info..."
    ("foreach" body line 121)
    invoked from within
"foreach pass $multipass {

        # multipass_name is set for `record_test' to use (see framework.exp).
        if { [lindex $pass 0] != "" } {
            set multipass_..."
    ("foreach" body line 51)
    invoked from within
"foreach current_target $target_list {
    verbose "target is $current_target"
    set current_target_name $current_target
    set tlist [split $curren..."
    (file "/opt/gnu/share/dejagnu/runtest.exp" line 1625)
make[4]: *** [check-gdb.xml] Error 1
make[4]: Leaving directory `/xxx/gnu/gdb/objdir/gdb/testsuite'
make[3]: Leaving directory `/xxx/gnu/gdb/objdir/gdb/testsuite'
make[2]: Leaving directory `/xxx/gnu/gdb/objdir/gdb'
make[1]: Nothing to be done for `check-target'.
make[1]: Leaving directory `/xxx/gnu/gdb/objdir'
Thu Nov 18 19:23:54 EST 2010

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2010-11-19  1:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 22:40 danglin at gcc dot gnu.org [this message]
2011-01-05 20:58 ` [Bug gdb/12238] " tromey at redhat dot com
2011-01-05 21:26 ` dave at hiauly1 dot hia.nrc.ca
2012-12-14 15:46 ` tromey at redhat dot com

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=bug-12238-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).