Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: David Smith <dsmith@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, GDB <gdb@sourceware.org>,
	       systemtap@sourceware.org
Subject: Re: ptrace-tests
Date: Wed, 31 Aug 2016 16:44:00 -0000	[thread overview]
Message-ID: <20160831164420.GA18750@host1.jankratochvil.net> (raw)
In-Reply-To: <7d05062f-2998-c10e-1006-0b9a267ecf4e@redhat.com>

On Wed, 31 Aug 2016 18:38:25 +0200, David Smith wrote:
> On 08/31/2016 10:36 AM, Yao Qi wrote:
> > we have a ptrace regression tests here
> > https://sourceware.org/systemtap/wiki/utrace/tests, and I can
> > still checkout code from cvs repo.  What is the mailing list to
> > post patches?

I do not know about a mailing list.  The contact person may be myself.


> I didn't know those tests existed. It looks like no one has touched them
> since around 2012.

The last CVS ChangeLog entry is:
2015-11-23 10:00  jkratoch
        * tests/bogus-echild.c:
        tests/bogus-echild.c: Fix env(TESTTIME) not to be multiplied by DEFAULT_TESTTIME.
          Make DEFAULT_TESTTIME unconditional.
          Remove DEFAULT_LOOPS support.


> If anyone would be still interested in them, I'd say it would be the
> ptrace() syscall kernel maintainers.

It should be probably moved to linux-2.6/tools/testing/selftests/ptrace/ but
it needs some cleanups first which nobody has done so far.


Jan


  reply	other threads:[~2016-08-31 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 15:36 ptrace-tests Yao Qi
2016-08-31 16:38 ` ptrace-tests David Smith
2016-08-31 16:44   ` Jan Kratochvil [this message]
2016-09-02  9:47     ` ptrace-tests Yao Qi
2016-09-02 10:09       ` ptrace-tests Jan Kratochvil
2016-09-02 10:15         ` ptrace-tests Yao Qi

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=20160831164420.GA18750@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dsmith@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --cc=systemtap@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