From: Demetrios Tsillas <jtsillas@enterasys.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] debugging skas
Date: Tue, 23 Sep 2003 14:16:29 -0400 [thread overview]
Message-ID: <3F708DFD.3050608@enterasys.com> (raw)
I run linux under gdb with skas mode. Prior to running I disable
handling of SIGSEGV and SIGUSR1. Linux runs OK and I can
hit breakpoints and debug.
But, if I want to interrupt the uml by typing cntrl-C, it will not be
able to continue. Gdb says the program exited normally. Somehow
SIGINT is not being handled correctly?
thanks for your help.
-Jim.
(gdb) run ubd0=/tmp/cow.1,/usr/src/root_fs.0.2 mem=256m eth0=mcast
Program received signal SIGTRAP, Trace/breakpoint trap.
0xa000d000 in _start ()
(gdb) cont
^C
Program received signal SIGINT, Interrupt.
0xa02039cc in __libc_waitpid (pid=4244, stat_loc=0xad3bfcc0, options=2)
at ../sysdeps/unix/sysv/linux/waitpid.c:28
(gdb) c
Program exited normally.
(gdb)
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-09-23 18:13 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=3F708DFD.3050608@enterasys.com \
--to=jtsillas@enterasys.com \
--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