mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: sameer.abhinkar@intel.com, linux-kernel@vger.kernel.org,
	Matt Mackall <mpm@selenic.com>
Subject: Re: KGDB question
Date: Thu, 17 Mar 2005 14:29:58 -0800	[thread overview]
Message-ID: <20050317142958.462822d2.akpm@osdl.org> (raw)
In-Reply-To: <200503171409.07290.jbarnes@engr.sgi.com>

Jesse Barnes <jbarnes@engr.sgi.com> wrote:
>
> > kgdb patches are maintained in -mm kernels.
> >
> > Patches are in
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11
> >-mm1/broken-out/*kgdb*
> >
> > And the patch application order is described in
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11
> >-mm1/patch-series -
> 
> What's the latest status on these?  Last I heard, some cleanup was going to 
> happen to make kgdb suitable for the mainline, did that ever happen?

It part-happened, then the effort seemed to die.

>  Also, 
> it would be nice if I could connect to a remote kernel running the kgdb stubs 
> w/o having to run gdb on the same ethernet segment.  Would that be difficult 
> to fix?

<tries to remember how ethernet works>

Maybe we'd have to teach kgdboe to arp for the remote debug host.  I think
Matt was talking about that a while back.

<tries to remember how ethernet switches work>

If switches send the destination MAC address through unchanged then maybe
the problem is that the switch simply doesn't know the MAC address of the
remote debug host yet?  If the switch has its own MAC address (it doesn't,
does it), or if it's actually a router then perhaps you should specify the
router's MAC address and not the remote debug host's.

  reply	other threads:[~2005-03-17 22:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 20:06 Abhinkar, Sameer
2005-03-17 21:54 ` Andrew Morton
2005-03-17 22:09   ` Jesse Barnes
2005-03-17 22:29     ` Andrew Morton [this message]
2005-03-17 22:55       ` Matt Mackall
2005-03-22 16:46       ` Tom Rini

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=20050317142958.462822d2.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=sameer.abhinkar@intel.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

all inboxes | Powered by JetHome®