From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
Will Deacon <will.deacon@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3] gdbserver: uclinux: pull in ptrace offset definitions from asm/ptrace.h
Date: Fri, 27 Apr 2012 07:25:00 -0000 [thread overview]
Message-ID: <20120427071106.GA30469@host2.jankratochvil.net> (raw)
In-Reply-To: <4F99A002.9020807@redhat.com>
On Thu, 26 Apr 2012 21:20:34 +0200, Pedro Alves wrote:
> Indeed. I've now peeked at strace's sources, and they do some butt-ugly
> #ifdef'ery to pick sys/ptrace.h vs asm/ptrace.h depending on arch x libc.
> So fine with me to forget about including the header at the top, until we
> find some other need.
in
http://sourceware.org/systemtap/wiki/utrace/tests
the ptrace.h inclusion compatible back to RHEL-4 and across
x86*/ppc*/s390*/ia64 ended up as:
#ifdef __ia64__
#define ia64_fpreg ia64_fpreg_DISABLE
#define pt_all_user_regs pt_all_user_regs_DISABLE
#endif /* __ia64__ */
#include <sys/ptrace.h>
#ifdef __ia64__
#undef ia64_fpreg
#undef pt_all_user_regs
#endif /* __ia64__ */
#include <linux/ptrace.h>
#include <sys/types.h>
#include <sys/user.h>
#if defined __i386__ || defined __x86_64__
#include <sys/debugreg.h>
#endif
It may be partially unrelated as there were needed more symbols than in
gdbserver, OTOH it does not have to solve non-Linux platforms.
Regards,
Jan
next prev parent reply other threads:[~2012-04-27 7:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 18:06 Will Deacon
2012-04-26 18:11 ` Pedro Alves
2012-04-26 18:15 ` Mike Frysinger
2012-04-26 18:23 ` Pedro Alves
2012-04-26 18:26 ` Mike Frysinger
2012-04-26 18:34 ` Pedro Alves
2012-04-26 18:36 ` Will Deacon
2012-04-26 18:53 ` Pedro Alves
2012-04-26 18:59 ` Pedro Alves
2012-04-26 19:06 ` Mike Frysinger
2012-04-26 19:26 ` Pedro Alves
2012-04-27 7:25 ` Jan Kratochvil [this message]
2012-04-26 18:37 ` Will Deacon
2012-04-26 19:36 ` Pedro Alves
2012-04-27 10:32 ` Will Deacon
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=20120427071106.GA30469@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=vapier@gentoo.org \
--cc=will.deacon@arm.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