From: Jeff Dike <jdike@addtoit.com>
To: Sebastian <seb@exse.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] crash with uml-2.6.8.1-um1
Date: Thu, 09 Sep 2004 23:55:23 -0400 [thread overview]
Message-ID: <200409100355.i8A3tNg1005671@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 02 Sep 2004 12:24:08 +0200." <4136F4C8.4040905@exse.net>
seb@exse.net said:
> I know that this does not help to find the problem, what can I do ?
> How to produce a stacktrace ?
Putting a breakpoint on panic and get a backtrace when it hits.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-09-10 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 10:24 [uml-devel] crash with uml-2.6.8.1-um1 Sebastian
2004-09-10 3:55 ` Jeff Dike [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=200409100355.i8A3tNg1005671@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=seb@exse.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox