Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add sparc64-linux sigtramp support
Date: Thu, 21 Apr 2005 19:29:00 -0000	[thread overview]
Message-ID: <20050421122250.6108168c.davem@davemloft.net> (raw)
In-Reply-To: <200504211923.j3LJNHo6010891@elgar.sibelius.xs4all.nl>

On Thu, 21 Apr 2005 21:23:17 +0200 (CEST)
Mark Kettenis <mark.kettenis@xs4all.nl> wrote:

> FYI, "issue" #1 is to make sure the frame base address matches with
> what the DWARF2 unwinder thinks.

Right.

> I'm not thrilled by documenting the "struct pt_regs" layout.  The
> constants already are there in the code.  I think it is more important
> to document where to find the offsets.  I also think it is better to
> point people to "struct sigcontext" instead of "struct pt_regs".
> That's where I got them from.  Can you change the comment in something
> like:
> 
> /* Offsets from <bits/sigcontext.h>.  */
> 
> ?
> 
> Otherwise this is ok, so please go ahead.

Sure, I'll fix this all up.  Thanks for reviewing.  I'd like to convert
this stuff over to the cleaner infrastructure PPC and MIPS linux targets
use, it might mean ditching the solaris tdep sharing though since they
sniff the sigtramps slightly differently.  It's kind of weird that we
let the solaris code register it's sniffer in the chain on linux targets
even though the linux sniffer is registered such that it trumps the solaris
one.

> P.S. I'm close to enabling the DWARF2 unwinder for SPARC, but there
> still are a few issues that I have to solve yet.  None of these affect
> Linux/sparc64.  I can send you a patch to test if you want.

Funny, I started playing around with the DWARF2 unwinder last night
as well on Sparc.  It interacted badly with the signal trampoline
sniffers but otherwise mostly worked, and that's as far as I got before
I went to bed.

Please send me your test patch and what issues you are aware of, I can
likely work on fixing them today/tonight.


  reply	other threads:[~2005-04-21 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21  3:51 David S. Miller
2005-04-21 19:23 ` Mark Kettenis
2005-04-21 19:29   ` David S. Miller [this message]
2005-04-21 21:20     ` Mark Kettenis
2005-04-21 21:41       ` David S. Miller
2005-04-21 21:57         ` Mark Kettenis
2005-04-21 22:04           ` David S. Miller
2005-04-21 21:55       ` David S. Miller
2005-04-21 22:09         ` Mark Kettenis
2005-04-22 22:45           ` David S. Miller
2005-04-23 12:33             ` Mark Kettenis
2005-04-23 17:47               ` David S. Miller

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=20050421122250.6108168c.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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