From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
sameer.abhinkar@intel.com, linux-kernel@vger.kernel.org,
Matt Mackall <mpm@selenic.com>
Subject: Re: KGDB question
Date: Tue, 22 Mar 2005 09:46:58 -0700 [thread overview]
Message-ID: <20050322164657.GD25923@smtp.west.cox.net> (raw)
In-Reply-To: <20050317142958.462822d2.akpm@osdl.org>
On Thu, Mar 17, 2005 at 02:29:58PM -0800, Andrew Morton wrote:
> 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.
Mutter, mutter, curse, mutter.
We got stuck on things like backtrace going on forever, and then trying
to find a way to get GDB to believe we want it to stop backtracing. I
think we've finally got that, in a way the GDB folks will approve and
won't horribly clutter the kernel.
We also got stuck on catching memory faults cleanly since it seems the
set_fs(KERNEL_DS) trick we used to use (and I swear worked), stopped
working around 2.6.10, but I haven't found time to go back and verify
when it stopped working.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-03-22 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 20:06 KGDB question Abhinkar, Sameer
2005-03-17 21:54 ` Andrew Morton
2005-03-17 22:09 ` Jesse Barnes
2005-03-17 22:29 ` Andrew Morton
2005-03-17 22:55 ` Matt Mackall
2005-03-22 16:46 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-06 5:40 KGDB Question Jason Hanna
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=20050322164657.GD25923@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=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 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.