Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Reanimate XStormy16
Date: Fri, 24 Sep 2004 07:36:00 -0000	[thread overview]
Message-ID: <20040924073720.GQ12802@cygbert.vinschen.de> (raw)
In-Reply-To: <4153072B.nail1U621LNEF@mindspring.com>

Michael,

On Sep 23 13:26, Michael Chastain wrote:
> Corinna Vinschen <vinschen@redhat.com> wrote:
> > # of expected passes            8954
> > # of unexpected failures        119
> > # of expected failures          41
> > # of known failures             40
> > # of unresolved testcases       4
> > # of untested testcases         5
> > # of unsupported tests          29
> 
> That is pretty good ... better than native hppa2.0w-hp-hpux11.11
> for sure!
> 
> Hmmm, the UNSUPPORTED count looks high.
> It should be about 3 or 4.

Please note that XStormy16 is a very tiny 16 bit target.  No signal
support, no core file support, no shared libs, no libstdc++-v3,
no threads.

  UNSUPPORTED: gdb.ada/null_record.exp: Ada compilation failed [...]
  UNSUPPORTED: gdb.base/auxv.exp: generate native core dump
  UNSUPPORTED: gdb.base/auxv.exp: info auxv on native core dump
  UNSUPPORTED: gdb.base/auxv.exp: matching auxv data from live and core
  UNSUPPORTED: gdb.base/auxv.exp: info auxv on gcore-created dump
  UNSUPPORTED: gdb.base/auxv.exp: matching auxv data from live and gcore
  UNSUPPORTED: gdb.base/gcore.exp: gdb does not support gcore on this target
  UNSUPPORTED: gdb.base/info-proc.exp: gdb does not support info proc on this target
  UNSUPPORTED: gdb.base/list.exp: list default lines around main
  UNSUPPORTED: gdb.base/reread.exp: run to foo() second time
  UNSUPPORTED: gdb.base/reread.exp: second pass: GDB should check for changes before running
  UNSUPPORTED: gdb.base/scope.exp: print 'scope0.c'::filelocal_bss before run
  UNSUPPORTED: gdb.base/sepdebug.exp: cannot produce separate debug info files
  UNSUPPORTED: gdb.objc/basicclass.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.objc/nondebug.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.objc/objcdecode.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/bp_in_thread.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/gcore-thread.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/killed.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/manythreads.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/print-threads.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/pthread_cond_wait.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/schedlock.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/staticthreads.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/switch-threads.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/thread-specific.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/thread_check.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/tls-shared.exp: Couldn't compile [...]
  UNSUPPORTED: gdb.threads/tls.exp: Couldn't compile [...]

> Can you look in your gdb.sum and count the ERROR and WARNING lines?
> 
>   grep -c ERROR gdb.sum

12

>   grep -c WARNING gdb.sum

39

See the below list.  If you're interested in more details, I can
send you the gdb.log file.

gdb.base/auxv.exp:

  ERROR: Undefined command "gcore [...]testsuite/gdb.base/auxv.gcore".
  UNRESOLVED: gdb.base/auxv.exp: gcore

gdb.base/default.exp:

  WARNING: Skipping backtrace and break tests because of GDB stub.

gdb.base/sigbpt.exp:

  WARNING: Testcase compile failed [...]
  ERROR: (timeout) GDB never initialized after 10 seconds.
  WARNING: remote_expect statement without a default case?!
  ERROR: couldn't unload file in [...]
  ERROR: couldn't load [...]
  ERROR: Delete all breakpoints [...]
  UNRESOLVED: gdb.base/sigbpt.exp: setting breakpoint at main (timeout)
  WARNING: remote_expect statement without a default case?!
  ERROR: tcl error sourcing [...]/gdb.base/sigbpt.exp.
  ERROR: can't read "segv_addr": no such variable while executing [...]

gdb.base/signull.exp:

  WARNING: Testcase compile failed [...]
  ERROR: (timeout) GDB never initialized after 10 seconds.
  WARNING: remote_expect statement without a default case?!
  ERROR: couldn't unload file in [...]
  ERROR: couldn't load [...]
  ERROR: Delete all breakpoints [...]
  UNRESOLVED: gdb.base/signull.exp: setting breakpoint at main (timeout)
  WARNING: remote_expect statement without a default case?!
  ERROR: Jump to start() failed (timeout)
  UNRESOLVED: gdb.base/signull.exp: (timeout) rerun to main

gdb.mi/gdb701.exp, gdb.mi/gdb792.exp, gdb.mi/mi-cli.exp,
gdb.mi/mi-console.exp, gdb.mi/mi-disassemble.exp, gdb.mi/mi-eval.exp,
gdb.mi/mi-read-memory.exp, gdb.mi/mi-return.exp, gdb.mi/mi-simplerun.exp,
gdb.mi/mi-stack.exp, gdb.mi/mi-stepi.exp, gdb.mi/mi-until.exp,
gdb.mi/mi-var-block.exp, gdb.mi/mi-var-child.exp, gdb.mi/mi-var-cmd.exp,
gdb.mi/mi-var-display.exp, gdb.mi/mi-watch.exp, gdb.mi/mi2-cli.exp,
gdb.mi/mi2-console.exp, gdb.mi/mi2-disassemble.exp, gdb.mi/mi2-eval.exp,
gdb.mi/mi2-read-memory.exp, gdb.mi/mi2-return.exp, gdb.mi/mi2-simplerun.exp,
gdb.mi/mi2-stack.exp, gdb.mi/mi2-stepi.exp, gdb.mi/mi2-until.exp,
gdb.mi/mi2-var-block.exp, gdb.mi/mi2-var-child.exp, gdb.mi/mi2-var-cmd.exp,
gdb.mi/mi2-var-display.exp, gdb.mi/mi2-watch.exp:

 WARNING: Using CLI jump command, expect run-to-main FAIL


HTH,
Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat, Inc.


  reply	other threads:[~2004-09-24  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 17:02 Corinna Vinschen
2004-09-23 17:25 ` Michael Chastain
2004-09-24  7:36   ` Corinna Vinschen [this message]
2004-09-24 18:13     ` Michael Chastain

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=20040924073720.GQ12802@cygbert.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gdb-patches@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