linux-um archives
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Is there an easy way to do a stack dump on UML?
Date: Fri, 2 Dec 2005 14:12:21 -0600	[thread overview]
Message-ID: <200512021412.21539.rob@landley.net> (raw)

I don't know how to send sysrq through the stdio console.

I have a reproducable hang (well, I did this morning and think I can recreate 
it).  It's gcc 4.0.2 attempting to statically link busybox (the allyesconfig 
version), it just goes off into la-la land.  left it for an hour and no 
progress, and UML is not eating noticeable CPU according to top (it roughly 
correlates with the timer interrupt load).

I'd like to see what the heck this sucker thinks it's doing, but it's kinda 
tricky to strace "make".  (Too many forks.)

Rob
-- 
Steve Ballmer: Innovation!  Inigo Montoya: You keep using that word.
I do not think it means what you think it means.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2005-12-02 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 20:12 Rob Landley [this message]
2005-12-03  2:59 ` [uml-devel] Is there an easy way to do a stack dump on UML? Blaisorblade
2005-12-03  3:44   ` Rob Landley
2005-12-03  6:00     ` Jeff Dike
2005-12-04 17:50       ` Rob Landley

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=200512021412.21539.rob@landley.net \
    --to=rob@landley.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