public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Maxim Grigoriev <maxim2405@gmail.com>
Cc: Pedro Alves <palves@redhat.com>,
	gdb-patches@sourceware.org,	Marc Gauthier <marc@tensilica.com>,
	Dror Maydan <maydan@tensilica.com>
Subject: Re: [PATCH] gdb: xtensa: fix build
Date: Thu, 16 Jan 2014 20:27:00 -0000	[thread overview]
Message-ID: <20140116202727.GH4602@tarshish> (raw)
In-Reply-To: <CAC3St3Du78bPPpczNwdV-TvCN-egk1kFn=L9tYveazDdse-dnA@mail.gmail.com>

Hi Maxim,

On Thu, Jan 16, 2014 at 12:11:41PM -0800, Maxim Grigoriev wrote:
> Hello Pedro and Baruch,
> 
> I actually haven't been doing Xtensa GDB maintenance for quite some time
> now since I left Tensilica.

Since xtensa-linux-nat.c used PTRACE_GETXTREGS since the beginning, and since 
sys/ptrace.h (at least on uClibc) never defined this value, the question is 
simply how did you build gdb at the time?

I should note that Buildroot is carrying this patch for more than a year now.

> Let's ask Marc and Dror. I've included them on the list.
> 
> Marc, Dror : Who is doing Xtensa GDB maintenance now ? If you want me to
> help, I can do it.

baruch

> On Thu, Jan 16, 2014 at 9:01 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > Hi Pedro,
> >
> > Thanks for reviewing.
> >
> > On Thu, Jan 16, 2014 at 04:46:03PM +0000, Pedro Alves wrote:
> > > On 01/16/2014 01:01 PM, Baruch Siach wrote:
> > > > We need asm/ptrace.h for PTRACE_GETXTREGS.
> > >
> > > Did something change?  Clearly this wasn't needed before.
> >
> > I'm not sure what has changed. As far as I can see sys/ptrace.h never had
> > PTRACE_GETXTREGS defined. Maybe Maxim has a clue (Added to Cc).
> >
> > 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 -

  parent reply	other threads:[~2014-01-16 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 13:02 Baruch Siach
2014-01-16 16:46 ` Pedro Alves
2014-01-16 17:01   ` Baruch Siach
     [not found]     ` <CAC3St3Du78bPPpczNwdV-TvCN-egk1kFn=L9tYveazDdse-dnA@mail.gmail.com>
2014-01-16 20:27       ` Baruch Siach [this message]
2014-01-17 13:07         ` Pedro Alves
2014-01-17 13:11           ` Baruch Siach

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=20140116202727.GH4602@tarshish \
    --to=baruch@tkos.co.il \
    --cc=gdb-patches@sourceware.org \
    --cc=marc@tensilica.com \
    --cc=maxim2405@gmail.com \
    --cc=maydan@tensilica.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).