Date: Tue, 23 Nov 2004 15:07:38 -0800
From: Andrew Morton <akpm@osdl.org>
To: "colin" <colin@realtek.com.tw>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I cannot stop execution by using "ctrl+c"
Message-Id: <20041123150738.0e243724.akpm@osdl.org>
In-Reply-To: <011501c4d14e$d00b1ce0$8b1a13ac@realtek.com.tw>
References: <011501c4d14e$d00b1ce0$8b1a13ac@realtek.com.tw>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1093
Lines: 24

"colin" <colin@realtek.com.tw> 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?

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/