Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Unwinder for OpenBSD/sparc64 kernel trap frames
Date: Sun, 31 Dec 2006 15:05:00 -0000	[thread overview]
Message-ID: <20061231150534.GA16449@nevyn.them.org> (raw)
In-Reply-To: <200612311236.kBVCacgf020195@brahms.sibelius.xs4all.nl>

On Sun, Dec 31, 2006 at 01:36:38PM +0100, Mark Kettenis wrote:
> Heh, I believe you raised the same question when I added the same code
> to i386 and amd64.  At that time I believe I convinced you that this
> was acceptable.

Oh right :-)  Shows you what my memory is worth these days.

> Adding Linux kernel debugging support is much harder.  The rate of
> change is much higher, there are kernel modules (which have a slightly
> odd format).  And of course Linux doesn't have kernel core dumps, so
> it would only be useful to debug a live kernel.

I'm not sure about all of these, except the last one - there's at least
one implementation of crash dumps for Linux.  It's still not common,
though, more's the pity.

> > Anyway, I have some thoughts on how to extend the unwind mechanism so
> > that the OpenBSD kernel could ship a script that knew how to unwind its
> > trap frames.
> 
> Did you really mean to say OpenBSD here?

Well, *BSD.  I mean, specifically, a script that does the same thing
the patch to sparc64obsd-tdep.c does.  Whether it actually gets bundled
with OpenBSD or with GDB is an interesting question, I guess :-)

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-12-31 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31  1:28 Mark Kettenis
2006-12-31  2:23 ` Daniel Jacobowitz
2006-12-31 12:36   ` Mark Kettenis
2006-12-31 15:05     ` Daniel Jacobowitz [this message]

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=20061231150534.GA16449@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --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