From: "colin" <colin@realtek.com.tw>
To: "Andrew Morton" <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: I cannot stop execution by using "ctrl+c"
Date: Mon, 29 Nov 2004 14:25:04 +0800 [thread overview]
Message-ID: <007101c4d5dc$29cb0970$8b1a13ac@realtek.com.tw> (raw)
In-Reply-To: <20041123150738.0e243724.akpm@osdl.org>
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" <akpm@osdl.org>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-kernel@vger.kernel.org>
Sent: Wednesday, November 24, 2004 7:07 AM
Subject: Re: I cannot stop execution by using "ctrl+c"
> "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.
prev parent reply other threads:[~2004-11-29 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 11:23 colin
2004-11-23 14:02 ` Jan Engelhardt
2004-11-23 23:07 ` Andrew Morton
2004-11-29 6:25 ` colin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007101c4d5dc$29cb0970$8b1a13ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®