Skip to contentSkip to conversation

I cannot stop execution by using "ctrl+c"

DISCUSSION colin 3 participants 4 messages Nov 23, 2004 – Nov 29, 2004

lore
Share & tools
lore

colin

author
#0 lore raw

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

#1 lore raw
Quoted 9 lines

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?

Since when does GDB *run* the kernel, if, well, the Kernel runs itself?

Jan Engelhardt

Signature · 2 lines
Gesellschaft f羹r Wissenschaftliche Datenverarbeitung
Am Fassberg, 37077 G繹ttingen, www.gwdg.de
#2 lore raw
In reply to colin
Quoted 9 lines · colin

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?

This means that the kgdb stub is no longer intercepting the serial interrupts. This tends to happen when someone makes changes to the serial layer and the kgdb patch isn't updated to reflect those changes.

You failed to mention the kernel version. The kgdb stub in 2.6.10-rc2-mm3 should work OK.

Sometimes, disabling the serial drivers in .config will help.

author
#3 lore raw

Hi Andrew,
I had tried to disable serial drivers and it still didn't work.

The platform is the malta board with MIPS CPU.
I also tried to use newer kernel 2.6.10-rc2-mipscvs and the problem still exists.

Thanks and regards,
Colin

----- Original Message -----
From: "Andrew Morton" <[email protected]>
To: "colin" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, November 24, 2004 7:07 AM
Subject: Re: I cannot stop execution by using "ctrl+c"

Quoted 19 lines
Quoted 9 lines · colin

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?

This means that the kgdb stub is no longer intercepting the serial interrupts. This tends to happen when someone makes changes to the serial layer and the kgdb patch isn't updated to reflect those changes.

You failed to mention the kernel version. The kgdb stub in 2.6.10-rc2-mm3 should work OK.

Sometimes, disabling the serial drivers in .config will help.