From: "Vladimir A. Gurevich" <vag@paulidav.org>
To: colin <colin@realtek.com.tw>
Cc: linux-mips@linux-mips.org
Subject: Re: KGDB: I cannot stop execution by using "ctrl+c"
Date: Wed, 03 Nov 2004 07:21:02 -0800 [thread overview]
Message-ID: <4188F75E.9010105@paulidav.org> (raw)
In-Reply-To: <01e101c4c182$5d0f2780$8b1a13ac@realtek.com.tw>
Hello Colin,
colin wrote:
>When using gdb to debug Linux kernel, I found that it cannot be stopped
>temporarily by using "ctrl+c".
>After the first strike of "ctrl+c", nothing happen.
>After the second, Linux kernel will show these messages:
> Interrupted while waiting for the program.
> Give up (and stop debugging it)? (y or n)
>If choose yes, kernel will totally stop and it goes back to gdb shell.
>How can I stop kernel temporarily and then resume it?
>
You should use the following command in GDB:
set remotebreak 1
After that it will start to behave as you expect it to, i.e. it will
interrupt the kernel as soon as you press CTRL-C.
Happy hacking,
Vladimir
next prev parent reply other threads:[~2004-11-03 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 8:51 KGDB: I cannot stop execution by using "ctrl+c" colin
2004-11-03 8:51 ` colin
2004-11-03 15:21 ` Vladimir A. Gurevich [this message]
2004-11-12 7:49 ` colin
2004-11-12 7:49 ` colin
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=4188F75E.9010105@paulidav.org \
--to=vag@paulidav.org \
--cc=colin@realtek.com.tw \
--cc=linux-mips@linux-mips.org \
/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.