Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Daniel Jacobowitz <drow@false.org>, Ulrich Weigand <uweigand@de.ibm.com>
Subject: [rfc] Define PTRACE_GETSIGINFO in linux-nat.c
Date: Tue, 02 Oct 2007 07:01:00 -0000	[thread overview]
Message-ID: <4701EC60.70702@de.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Hi,

the new save_siginfo() function from linux-nat.c breaks my build on

  Linux bbkeks 2.6.9-55.0.6.EL #1 Thu Aug 23 10:59:21 EDT 2007 i686 i686 i386 GNU/Linux

because PTRACE_GETSIGINFO isn't defined in the includes. The patch takes over definition of it from ppc-linux-nat.c


ChangeLog:

	* linux-nat.c (PTRACE_GETSIGINFO): Add define.

Tested on x86.

Is this ok to commit or would it be better to move it to a header (linux-nat.h ?) file and delete it from ppc-linux-nat.c as well to prevent 
redundancy?

Regards,
Markus

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com


[-- Attachment #2: diff-PTRACE_GETSIGINFO --]
[-- Type: text/plain, Size: 497 bytes --]

diff -urpN src/gdb/linux-nat.c dev/gdb/linux-nat.c
--- src/gdb/linux-nat.c	2007-10-01 09:00:51.000000000 +0200
+++ dev/gdb/linux-nat.c	2007-10-02 08:43:40.000000000 +0200
@@ -84,6 +84,10 @@
 #define __WALL          0x40000000 /* Wait for any child.  */
 #endif
 
+#ifndef PTRACE_GETSIGINFO
+#define PTRACE_GETSIGINFO    0x4202
+#endif
+
 /* The single-threaded native GNU/Linux target_ops.  We save a pointer for
    the use of the multi-threaded target.  */
 static struct target_ops *linux_ops;

             reply	other threads:[~2007-10-02  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02  7:01 Markus Deuling [this message]
2007-10-02 11:41 ` Daniel Jacobowitz
2007-10-02 16:34   ` Ulrich Weigand

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=4701EC60.70702@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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