From: Baruch Siach <baruch@tkos.co.il>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Maxim Grigoriev <maxim2405@gmail.com>,
Marc Gauthier <marc@cadence.com>,
Dror Maydan <maydan@cadence.com>, Woody LaRue <larue@cadence.com>,
Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH v2] gdb: xtensa: fix linux ptrace includes
Date: Wed, 22 Jan 2014 04:52:00 -0000 [thread overview]
Message-ID: <20140122045202.GM12751@tarshish> (raw)
In-Reply-To: <52DD0D6C.1040309@redhat.com>
Hi Pedro,
On Mon, Jan 20, 2014 at 11:50:04AM +0000, Pedro Alves wrote:
> On 01/19/2014 07:53 AM, Baruch Siach wrote:
> > Currently, xtensa code using the Linux ptrace interface only include
> > sys/ptrace.h. This file comes from the C library (glibc and uClibc, at least),
> > and includes a declaration of the ptrace() functions, along with some cross
> > architecture constants that are mostly copied from the file located at
> > include/uapi/linux/ptrace.h in recent Linux kernels.
> >
> > For xtensa specific constants like PTRACE_GETXTREGS and PTRACE_SETXTREGS the
> > asm/ptrace.h include from the Linux kernel UAPI is needed. The code in
> > gdbserver xtensa specific part doesn't call ptrace() directly, so we can
> > remove the unneeded sys/ptrace.h include. The gdb xtensa specific code needs
> > both headers, since it calls ptrace().
>
> Pushed, thanks.
It would be nice to have this and the other xtensa fix in the 7.6 and 7.7
branches as well.
Thanks,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-01-22 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 7:53 Baruch Siach
2014-01-20 12:20 ` Pedro Alves
2014-01-22 4:52 ` Baruch Siach [this message]
2014-01-22 12:36 ` Pedro Alves
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=20140122045202.GM12751@tarshish \
--to=baruch@tkos.co.il \
--cc=chris@zankel.net \
--cc=gdb-patches@sourceware.org \
--cc=larue@cadence.com \
--cc=marc@cadence.com \
--cc=maxim2405@gmail.com \
--cc=maydan@cadence.com \
--cc=palves@redhat.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