From: "Michael Richardson" <mcr@sandelman.ottawa.on.ca>
To: user-mode-linux-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] debugging skas kernels
Date: Sat, 09 Apr 2005 11:28:43 -0400 [thread overview]
Message-ID: <5595.1113060523@marajade.sandelman.ottawa.on.ca> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
I know that I can invoke skas kernels like any other process.
However, I find this a bit of a pain. I like to debug under Xemacs, and
I don't want the terminal directed to my emacs buffer, and the command
line arguments are kind of complex.
Is there a reason I can't just "attach" the process?
Could we make "debug" or "gdb" command line cause a pause() in the code,
near startup?
I'll do that and submit a patch if there isn't something I'm missing.
- --
] Michael Richardson Xelerance Corporation, Ottawa, ON | firewalls [
] mcr @ xelerance.com Now doing IPsec training, see |net architect[
] http://www.sandelman.ca/mcr/ www.xelerance.com/training/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQlf0qYqHRg3pndX9AQF8lQQA5o1EB2Kt7veqCpSjCNZf8ztdohSwMNA6
wD2K9H5MRZ8cgy1bIBCopOb5Is2Xogk7t2FnMwojecQLZX6HfBBTkBcsTDA73uPt
VghywKS4ClNhBYBTiub1oCnGtsR/OOS++kIvsEoyRTJP8fwTQ6Q/hQYYQ7txP4KU
z/9cmvp7t68=
=uRWI
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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-04-09 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5595.1113060523@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--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