From: "M R Swami Reddy" <MR.Swami.Reddy@nsc.com>
To: "Jim Blandy" <jimb@red-bean.com>, jimblandy@gmail.com
Cc: gdb@sourceware.org
Subject: Re: gdb testsuite
Date: Tue, 29 Jan 2008 06:07:00 -0000 [thread overview]
Message-ID: <479EC263.3060107@nsc.com> (raw)
In-Reply-To: <8f2776cb0801281050w4ae2d83fw53b793ba633302e1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi Jim,
Thank you very much for your response.
> One should be able to run programs on the simulator by starting GDB on
> the program to be run, typing "target sim", and then "run". Does this
> work?
I am able to set the target as "sim", load the program and run it on
cr16 gdb simulator (ie cr16-elf-gdb). And I am able to execute a few
C standard test suites using this cr16-elf-gdb tool.
> When you type 'make check-gdb' at the top of your build tree, or 'make
> check' in the gdb/testsuite directory of the build tree, what is the
> output? Does it create a gdb.log file? What are its contents?
I did ran the "make check-gdb", but the below results displayed:
=========
=== gdb Summary ===
# of expected passes 162
# of unexpected failures 343
# of unresolved testcases 18
# of untested testcases 1
# of unsupported tests 12
==========
Please find the gdb.log as an attachment (file name: gdb.log.bz2).
Thanks,
Swami
[-- Attachment #2: gdb.log.bz2 --]
[-- Type: application/octet-stream, Size: 9610 bytes --]
next prev parent reply other threads:[~2008-01-29 6:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 10:14 M R Swami Reddy
2008-01-25 18:16 ` Jim Blandy
2008-01-28 5:07 ` M R Swami Reddy
2008-01-28 18:51 ` Jim Blandy
2008-01-29 6:07 ` M R Swami Reddy [this message]
2008-01-29 20:22 ` Jim Blandy
2008-01-30 12:56 ` M R Swami Reddy
2008-01-30 17:56 ` Jim Blandy
2008-01-30 19:53 ` Thiago Jung Bauermann
2008-01-30 23:54 ` Jim Blandy
2008-01-31 17:33 ` Thiago Jung Bauermann
2008-02-01 11:45 ` M R Swami Reddy
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 12:09 qinwei
1999-05-20 4:34 GDB testsuite Rajesh Maddali
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=479EC263.3060107@nsc.com \
--to=mr.swami.reddy@nsc.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.com \
--cc=jimblandy@gmail.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