From: Daniel Jacobowitz <drow@mvista.com>
To: Richard Brunelle <rbrunelle@envitech.com>
Cc: gdb@sources.redhat.com
Subject: Re: Ctrl-c problem
Date: Sun, 01 Dec 2002 13:35:00 -0000 [thread overview]
Message-ID: <20021201213555.GA13484@nevyn.them.org> (raw)
In-Reply-To: <3DE7D702.903@envitech.com>
On Fri, Nov 29, 2002 at 04:07:14PM -0500, Richard Brunelle wrote:
> Hi,
>
> I'm doing kernel debugging through the use of gdb running on a
> development machine and a gdb stub running on a target machine. The
> latter is acheive with the kgdb patch applied to a kernel 2.4.18. This
> patch allows me to connect a development PC to a target PC through a
> serial line. It allows me to remotely debug a patched kernel. The
> connection works fine, I'm able to connect gdb to the target machine at
> boot time (target remote /dev/tyS0). The problem is not hardware. I am
> able to step in the kernel code at this time. After a few step, I resume
> the execution of the kernel with the continue command.
>
> My problem comes when I want to stop the execution of the target kernel
> with gdb. Usually Ctrl-c is used to stop the execution of the running
> process. So I hit Ctrl-c but the kernel never stop.
>
> Is there any configuration for gdb to enable Ctrl-c?
>
> Does anyone ever experience this problem?
What's your target platform? C-c works using the x86 KGDB stub. I
don't know if it works on PowerPC, and it definitely doesn't work on
MIPS. This is a stub question.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-01 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 13:09 Richard Brunelle
2002-12-01 13:35 ` Daniel Jacobowitz [this message]
2002-12-02 8:20 ` Richard Brunelle
2002-12-02 8:25 ` Daniel Jacobowitz
2002-12-02 9:05 ` Richard Brunelle
2002-12-02 9:18 ` Daniel Jacobowitz
2002-12-02 9:27 ` Richard Brunelle
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=20021201213555.GA13484@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=rbrunelle@envitech.com \
/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