All of lore.kernel.org
 help / color / mirror / Atom feed
* KGDB: I cannot stop execution by using "ctrl+c"
@ 2004-11-03  8:51 ` colin
  0 siblings, 0 replies; 5+ messages in thread
From: colin @ 2004-11-03  8:51 UTC (permalink / raw)
  To: linux-mips


Hi all,
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?

Thanks and regards,
Colin

^ permalink raw reply	[flat|nested] 5+ messages in thread

* KGDB: I cannot stop execution by using "ctrl+c"
@ 2004-11-03  8:51 ` colin
  0 siblings, 0 replies; 5+ messages in thread
From: colin @ 2004-11-03  8:51 UTC (permalink / raw)
  To: linux-mips


Hi all,
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?

Thanks and regards,
Colin

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: KGDB: I cannot stop execution by using "ctrl+c"
  2004-11-03  8:51 ` colin
  (?)
@ 2004-11-03 15:21 ` Vladimir A. Gurevich
  2004-11-12  7:49     ` colin
  -1 siblings, 1 reply; 5+ messages in thread
From: Vladimir A. Gurevich @ 2004-11-03 15:21 UTC (permalink / raw)
  To: colin; +Cc: linux-mips

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: KGDB: I cannot stop execution by using "ctrl+c"
@ 2004-11-12  7:49     ` colin
  0 siblings, 0 replies; 5+ messages in thread
From: colin @ 2004-11-12  7:49 UTC (permalink / raw)
  To: Vladimir A. Gurevich; +Cc: linux-mips


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
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: KGDB: I cannot stop execution by using "ctrl+c"
@ 2004-11-12  7:49     ` colin
  0 siblings, 0 replies; 5+ messages in thread
From: colin @ 2004-11-12  7:49 UTC (permalink / raw)
  To: Vladimir A. Gurevich; +Cc: linux-mips


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
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-11-12  7:49 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2004-11-12  7:49   ` colin
2004-11-12  7:49     ` colin

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.