From: george anzinger <george@mvista.com>
To: David Wuertele <dave-gnus@bfnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to interactively break gdb debugging kernel over serial?
Date: Sat, 15 Feb 2003 23:14:08 -0800 [thread overview]
Message-ID: <3E4F3A40.3090502@mvista.com> (raw)
In-Reply-To: <m38ywia054.fsf@bfnet.com>
David Wuertele wrote:
> I'm debugging the kernel with gdb over a serial port. Breakpoints and
> stepping through code works great, except for the fact that once the
> kernel is running, I can't seem to use Control-C to stop it. Is there
> a keypress or other interactive way to break a running kernel?
>
> Thanks,
> Dave
>
Dave,
There are a great number of kgdb patches in the wild. You would help
us out a lot if you were to name the one you are using. If you are on
then 2.5 kernel I suggest you check out Andrew Morton's area and use
that one.
If you are using the one from source forge on a 2.4 kernel, there is a
mailing list for it that can be found at the same sourceforge site.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-02-16 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 23:45 [PATCH 2.5.60 2/9] Update parport class driver to new module loader API Bob Miller
2003-02-14 23:54 ` how to interactively break gdb debugging kernel over serial? David Wuertele
2003-02-16 7:14 ` george anzinger [this message]
2003-02-18 20:37 ` David Wuertele
2003-02-18 22:49 ` george anzinger
2003-02-15 11:16 ` [PATCH 2.5.60 2/9] Update parport class driver to new module loader API Christoph Hellwig
2003-02-17 17:15 ` Bob Miller
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=3E4F3A40.3090502@mvista.com \
--to=george@mvista.com \
--cc=dave-gnus@bfnet.com \
--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 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.