Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb@sources.redhat.com, Elena Zannoni <ezannoni@redhat.com>,
	Fernando Nasser <fnasser@redhat.com>
Subject: Re: zillions of testsuite failures
Date: Thu, 16 Jan 2003 00:31:00 -0000	[thread overview]
Message-ID: <15909.65114.643546.190982@localhost.redhat.com> (raw)
In-Reply-To: <ro165sq6j9h.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > Is anybody seeing lots of testsuite failures all of a sudden?  I'm
 > getting huge numbers; many, possibly all of them (e.g. every MI test
 > fails), seem to have to do with how GDB is invoked.  It seems like, at
 > some point, invocations start getting
 > 
 >   <directory>/testsuite/gdb.base/args 1 '' '' 3
 > 

Argh! that's my fault!!! Sorry.
Let me fix it.
I think I set a global and didn't reset it....

Elena


 > tacked onto them.  E.g. the last line of gdb.sum is:
 > 
 > /extra/gdb/mirror/src/gdb/testsuite/../../gdb/gdb version  2003-01-15-cvs --args /extra/gdb/mirror/src/gdb/testsuite/gdb.base/args 1 '' '' 3
 > 
 > Looking at this a bit further, it seems like this 'global GDBFLAGS' that
 > args.exp sets is persisting for the rest of the entire test run.  So I
 > think there's something wrong with args.exp.
 > 
 > On a separate, I get the following results from gdb.base/advance.exp
 > 
 > Running ./gdb.base/advance.exp ...
 > PASS: gdb.base/advance.exp: advance line number
 > PASS: gdb.base/advance.exp: malformed advance
 > PASS: gdb.base/advance.exp: advance func
 > FAIL: gdb.base/advance.exp: advance function not called by current frame
 > FAIL: gdb.base/advance.exp: find line number containing "break here"
 > PASS: gdb.base/advance.exp: set breakpoint at call to func3
 > FAIL: gdb.base/advance.exp: continue to call to func3 in main
 > FAIL: gdb.base/advance.exp: advance function called as param
 > FAIL: gdb.base/advance.exp: advance with no argument
 > 
 > This happens before the args fiasco, so I think the failures are
 > legit.  Are they known?  I'll append the relevant part of my gdb.log
 > after my signature.
 > 
 > David Carlton
 > carlton@math.stanford.edu
 > 
 > (gdb) run 
 > Starting program: /extra/gdb/mirror/src/gdb/testsuite/gdb.base/advance 
 > 
 > Breakpoint 1, main () at gdb.base/advance.c:37
 > 37	  c = 5;
 > (gdb) list ./gdb.base/advance.c:1,1
 > No source file named ./gdb.base/advance.c.
 > (gdb) search advance this location
 > 38	  b = 3;    /* advance this location */
 > (gdb) advance 38
 > main () at gdb.base/advance.c:38
 > 38	  b = 3;    /* advance this location */
 > (gdb) PASS: gdb.base/advance.exp: advance line number
 > list ./gdb.base/advance.c:1,1
 > No source file named ./gdb.base/advance.c.
 > (gdb) search advance malformed
 > 43	  return 0; /* advance malformed */
 > (gdb) advance 43 then stop
 > Junk at end of arguments.
 > (gdb) PASS: gdb.base/advance.exp: malformed advance
 > advance func
 > func () at gdb.base/advance.c:18
 > 18	  x = x + 5;
 > (gdb) PASS: gdb.base/advance.exp: advance func
 > advance func3
 > main () at gdb.base/advance.c:41
 > 41	  func3 (); /* break here */
 > (gdb) FAIL: gdb.base/advance.exp: advance function not called by current frame
 > list ./gdb.base/advance.c:1,1
 > No source file named ./gdb.base/advance.c.
 > (gdb) search break here
 > Expression not found
 > (gdb) FAIL: gdb.base/advance.exp: find line number containing "break here"
 > break -1
 > Breakpoint 2 at 0x80484aa: file gdb.base/advance.c, line 40.
 > (gdb) PASS: gdb.base/advance.exp: set breakpoint at call to func3
 > continue
 > Continuing.
 > 
 > Program exited normally.
 > (gdb) FAIL: gdb.base/advance.exp: continue to call to func3 in main
 > advance foo
 > The program is not running.
 > (gdb) FAIL: gdb.base/advance.exp: advance function called as param
 > advance
 > The program is not running.
 > (gdb) FAIL: gdb.base/advance.exp: advance with no argument


  reply	other threads:[~2003-01-16  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16  0:17 David Carlton
2003-01-16  0:31 ` Elena Zannoni [this message]
2003-01-16  0:45 ` Elena Zannoni
2003-01-16  1:18   ` David Carlton
2003-01-16  1:52     ` Elena Zannoni
2003-01-16  0:56 ` Elena Zannoni

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=15909.65114.643546.190982@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=fnasser@redhat.com \
    --cc=gdb@sources.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