From: Marcel Moolenaar <marcel@xcllnt.net>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add libkvm interface support for NetBSD/i386 and OpenBSD/i386
Date: Sun, 27 Jun 2004 16:34:00 -0000 [thread overview]
Message-ID: <20040627163414.GB7790@dhcp50.pn.xcllnt.net> (raw)
In-Reply-To: <200406271623.i5RGN4Hd007746@elgar.kettenis.dyndns.org>
On Sun, Jun 27, 2004 at 06:23:04PM +0200, Mark Kettenis wrote:
> +
> + we reconstruct the register state as it would look when we just
> + returned from cpu_switch(). */
> +
Question: since this will do backtraces in the kernel, are there
plans to improve the frame sniffers (or frame sniffer framework)
to allow this code to add a sniffer for trapframes so that it's
possible to trace across them (if applicable) and also to improve
the termination of traces in the context of non-standard frames?
--
Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
next prev parent reply other threads:[~2004-06-27 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 16:23 Mark Kettenis
2004-06-27 16:34 ` Marcel Moolenaar [this message]
2004-06-27 17:02 ` Mark Kettenis
2004-06-27 17:39 ` Marcel Moolenaar
2004-06-27 19:02 ` Daniel Jacobowitz
2004-06-27 20:25 ` Mark Kettenis
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=20040627163414.GB7790@dhcp50.pn.xcllnt.net \
--to=marcel@xcllnt.net \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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