From: Yi Xu <yxu@suse.de>
To: ltp-list@lists.sf.net
Subject: [LTP] patch to define PTRACE_KILL and PTRACE_CONT
Date: Mon, 04 Oct 2010 15:08:02 +0200 [thread overview]
Message-ID: <4CA9D1B2.7070107@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
Hi,
this patch solves compiling error that appears with certain GCC version.
Regards,
Yi
--
Yi Xu yxu@suse.de
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
[-- Attachment #2: define_PTRACE_PARAM.patch --]
[-- Type: text/x-patch, Size: 540 bytes --]
--- testcases/kernel/syscalls/ptrace/ptrace.h.orig 2010-09-13 15:46:24.145591000 +0200
+++ testcases/kernel/syscalls/ptrace/ptrace.h 2010-09-13 16:18:40.732974000 +0200
@@ -4,6 +4,15 @@
#ifndef __LTP_PTRACE_H__
#define __LTP_PTRACE_H__
+#endif
+
+#ifndef __PTRACE_KILL__
+#define __PTRACE_KILL__
+#endif
+
+#ifndef __PTRACE_CONT__
+#define __PTRACE_CONT__
+#endif
#ifdef HAVE_SYS_PTRACE_H
# include <sys/ptrace.h>
@@ -30,4 +39,3 @@ typedef struct pt_regs ptrace_regs;
typedef struct user_regs_struct ptrace_regs;
#endif
-#endif
[-- Attachment #3: Type: text/plain, Size: 368 bytes --]
------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security
easier or more difficult to achieve? Read this whitepaper to separate the
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-10-04 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 13:08 Yi Xu [this message]
2010-10-04 13:48 ` [LTP] patch to define PTRACE_KILL and PTRACE_CONT Garrett Cooper
2010-10-06 8:02 ` Yi Xu
2010-10-06 16:42 ` Garrett Cooper
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=4CA9D1B2.7070107@suse.de \
--to=yxu@suse.de \
--cc=ltp-list@lists.sf.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.