| To: | colin <colin@realtek.com.tw> |
|---|---|
| Subject: | Re: KGDB: I cannot stop execution by using "ctrl+c" |
| From: | "Vladimir A. Gurevich" <vag@paulidav.org> |
| Date: | Wed, 03 Nov 2004 07:21:02 -0800 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <01e101c4c182$5d0f2780$8b1a13ac@realtek.com.tw> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <01e101c4c182$5d0f2780$8b1a13ac@realtek.com.tw> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 |
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 1After 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | KGDB: I cannot stop execution by using "ctrl+c", colin |
|---|---|
| Next by Date: | [PATCH] PCI support for Ocelot-3 in 2.6, Manish Lachwani |
| Previous by Thread: | KGDB: I cannot stop execution by using "ctrl+c", colin |
| Next by Thread: | Re: KGDB: I cannot stop execution by using "ctrl+c", colin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |