From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: ligang@sunnorth.com.cn
Cc: gdb@sourceware.org
Subject: Re: question about GDB test
Date: Fri, 04 Aug 2006 21:49:00 -0000 [thread overview]
Message-ID: <200608042149.k74LnQlL017861@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <OFC34589A3.D587308C-ON482571BF.0017B6AD-482571BF.0017C50D@sunnorth.com.cn> (ligang@sunnorth.com.cn)
> From: ligang@sunnorth.com.cn
> Date: Thu, 3 Aug 2006 12:19:37 +0800
>
> Hi, fellows,
>
> I am porting GDB to a new target. Definitely, test of GDB is an important
> issue.
> There are already some test suites in GDB source. Are they enouth?
> Need I to write some more test patterns for my special target and what
> kind of patterns should I write?
The current testsuite provides a pretty wide coverage of generic GDB
functionality. Making those tests PASS is a good start. But you
might want to add some tests for specific functionality of your
target.
Mark
prev parent reply other threads:[~2006-08-04 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 4:19 ligang
2006-08-03 9:28 ` Ramana Radhakrishnan
2006-08-04 21:49 ` Mark Kettenis [this message]
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=200608042149.k74LnQlL017861@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--cc=ligang@sunnorth.com.cn \
/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