All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Schaefer <frank.schafer@setuza.cz>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kernel serial debugging question
Date: 10 Jun 2002 07:37:02 +0200	[thread overview]
Message-ID: <1023687422.250.0.camel@ADMIN> (raw)
In-Reply-To: <20020607231856Z317361-22020+731@vger.kernel.org>

On Sat, 2002-06-08 at 01:18, Stephane Charette wrote:
> My question:
> ------------
> 
> Has any of this changed with the 2.4.x kernel?  I'm currently playing
> with 2.4.19-pre9.  Is there a "serial debugger" patch that has to be
> applied first, or is this support normally built-in?

I've set up kernel remote debugging for 2.4.18 not so far ago. The
procedure is the same as for the 2.2.* series. You should simply use the
patch for the kernel version you use.

> The reason I ask is because I don't see the option "Kernel support for
> GDB", which leads me to think that maybe this functionality actually
> came from a patch that was applied on top of 2.2.14.
> 
> While I'm at it:  is there a "better", or perhaps a "more popular"
> method of debugging the kernel?

On my development machine I've set up one kernel with the kgdb internal
debugger, one kernel with the gdb-patch and one unpatched kernel with
the usual debugging stuff enabled ( all kernels of the same version - of
course ). Which kernel to run depends on the kind of problem to solve,
and is IMHO more a question of personal taste.

Regards
Frank



      parent reply	other threads:[~2002-06-10  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 23:18 kernel serial debugging question Stephane Charette
2002-06-07 23:29 ` Andrew Morton
2002-06-10  5:37 ` Frank Schaefer [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=1023687422.250.0.camel@ADMIN \
    --to=frank.schafer@setuza.cz \
    --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.