Re: linux-2.6 x86_64 kgdb issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2006-05-31 at 23:01 +0200, Andi Kleen wrote:
> On Wednesday 31 May 2006 17:03, Tom Rini wrote:
> > On Wed, May 31, 2006 at 09:13:53AM +0200, Andi Kleen wrote:
> >
> > [snip]
> >
> > > Yes because you if modular works you don't need to build it in.
> > >
> > > Modular was working at some point on x86-64 for kdb and the original 2.6
> > > version of kgdb was nearly there too.
> >
> > FWIW, the only change the current version of kgdb makes that would
> > prevent it from being totally modular is the debugger_active check in
> > 
> 
> Can you post the patch and a description? 

It's maintained at SourceForge:

	http://sourceforge.net/projects/kgdb

Patches can be downloaded from:
	
	http://sourceforge.net/project/showfiles.php?group_id=5073

I suspect that you will likely want to add yourself to the
kgdb-bugreport mailing list.

	https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Mailing list is acting up; I've been having trouble posting due to
a mailserver problem; I contacted the SourceForge folks about it.

Andrew Morton has recently been taking snapshots and including them
in his mm series. It would be nice to get in "in order" and ready
for being merged up into the linux tree. When I applied the 2.6.13
patch I think I noticed some '#ifdef KGDB' code missing. I'd like 
to see the patch totally disabled by not configuring KGDB. The 
patch instructions are also a bit misleading, at least for 2.6.13;
I had to apply all of the patches in the series to avoid a lot a 
patch rejects. 

-piet

> 
> -Andi
-- 
---
[email protected]
--- Begin Message ---
Piet Delaney <[email protected]> wrote:
>
>  tried patching the latest stable kennel, 2.6.16.9 I thought, to
>  2.6.17.rc2 but got conflicts.

2.6.16.x is a branch, based on 2.6.16.

2.6.17-rcX is on the trunk.  The published diffs are against 2.6.16.

So you should have patched 2.6.16.


>  A few years ago Linus said he wanted to integrated the kgdb patch
>  but then stopped when he found our there were two patches. Now there
>  only seems to be one. Do you know why it's not being integrated into
>  the std linux kernel?

Nobody is doing the work to get the patches in order and merged up.  It'd
require a month or two moderately intense effort.

--- End Message ---

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux