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] Fix OpenBSD/i386 and OpenBSD/amd64 kernel trapframe unwinders
Date: Fri, 23 Dec 2005 18:46:00 -0000	[thread overview]
Message-ID: <20051222155657.GA5280@nevyn.them.org> (raw)
In-Reply-To: <200512221538.jBMFcErG006442@elgar.sibelius.xs4all.nl>

On Thu, Dec 22, 2005 at 04:38:14PM +0100, Mark Kettenis wrote:
> Yup.  There's a seperate entry point for every interrupt vector (hence
> the strncmp() for "Xintr") and on top of that, interrupts can come
> from both userland and from within the kernel.  I only want to
> terminate the backtrace when the interrupt came from userland.

That's no worse than for Linux.  This is actually all solvable with
DWARF-2, and in fact, George Anzinger wrote bits to do it for Linux. 
They're a bit disgusting, though (and I hope he'll agree if he's
reading this :-)

  http://source.mvista.com/~ganzinger/common_kgdb_cfi_annotations.patch

He makes use of dwarf2 branches; I'm not sure if he ended up needing an
extra physical stack frame anywhere, but I'm convinced it's possible to
do without that.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-12-22 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 17:07 Mark Kettenis
2005-12-22 19:45 ` Daniel Jacobowitz
2005-12-22 22:46   ` Mark Kettenis
2005-12-23  8:29     ` Daniel Jacobowitz
2005-12-23 14:29       ` Mark Kettenis
2005-12-23 18:46         ` 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=20051222155657.GA5280@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