linux-mips
[Top] [All Lists]

Re: KGDB: I cannot stop execution by using "ctrl+c"

To: "Vladimir A. Gurevich" <vag@paulidav.org>
Subject: Re: KGDB: I cannot stop execution by using "ctrl+c"
From: "colin" <colin@realtek.com.tw>
Date: Fri, 12 Nov 2004 15:49:13 +0800
Cc: <linux-mips@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <01e101c4c182$5d0f2780$8b1a13ac@realtek.com.tw> <4188F75E.9010105@paulidav.org>
Sender: linux-mips-bounce@linux-mips.org
Hi Vladimir,
It still cannot work using "set remotebreak 1".

Regards,
Colin


----- Original Message ----- 
From: "Vladimir A. Gurevich" <vag@paulidav.org>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-mips@linux-mips.org>
Sent: Wednesday, November 03, 2004 11:21 PM
Subject: Re: KGDB: I cannot stop execution by using "ctrl+c"


> 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
> 

<Prev in Thread] Current Thread [Next in Thread>