From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Allan Graves <allan.graves@oracle.com>
Subject: Re: [uml-devel] stack and scheduler patches
Date: Tue, 6 Sep 2005 11:37:04 -0400 [thread overview]
Message-ID: <20050906153704.GA5771@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200509041351.32837.blaisorblade@yahoo.it>
On Sun, Sep 04, 2005 at 01:51:32PM +0200, Blaisorblade wrote:
> Also, what is the difference between your "stack trace" patch, which adds a
> member to thread_struct, for each process, so I'd like a minimum of
> justification, and one of the sysrq options which does exactly this?
What this does, and sysrq t doesn't, is allow you to put a breakpoint
on that show_regs call and force a particular thread back into
context. Then you can poke around the stack with gdb. You could so
this in tt mode, but not previously in skas mode, and people have
missed this.
Jeff
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-09-06 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 23:06 [uml-devel] stack and scheduler patches Allan Graves
2005-09-02 16:59 ` Jeff Dike
2005-09-04 11:51 ` Blaisorblade
2005-09-06 15:37 ` Jeff Dike [this message]
2005-09-06 16:10 ` [uml-devel] sched and stack patch changelogs Allan Graves
2005-09-06 15:46 ` [uml-devel] stack and scheduler patches Allan Graves
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=20050906153704.GA5771@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=allan.graves@oracle.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.