Re: [Kgdb-bugreport] [KGDB PATCH][1/7] Add / use kernel/Kconfig.kgdb

[George Anzinger]

Jim Houston wrote:
> > Meanwhile, I would like to make a change to the gdb "info thread"
> > command to do a better job of displaying the threads.  Here is what
> > I am proposing:
> >
> > Gdb would work as it does now if the following set is not done.
> >
> > A new "set thread_level" command that would take the "bt" level to use
> > on the thread display.
> > A new "set thread_limits command that would take two expressions that
> > would reduce to two memory addresses.
>
>
> Hi George,
>
> I already did a bit of work in this space.  You might give my 
> gdb-thread-skip-frame.patch a try.  
>
> You can find it archived here:
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/gdb/gdb-6.0/gdb-thread-skip-frame.patch

I have been talking with the gdb folks and I think we are real close to having a 
solution that makes very minimal (if any) changes to gdb.  At this point we can 
write a couple of macros that do almost all that we need.  The only problem 
seems to be the number of lines per thread in the report.  So, the only change 
to gdb would be to suppress a carrage return in a couple of places.

It does require that we implement a new command in the stub, or rather, that we 
change the ThreadExtraInfo command to do the same thing with a different command.

I will keep you posted, or better yet, sign up for the gdb@xxxxxxxxxxxxxxxxxx 
mailing list and listen in.

-g
> Jim Houston

--
George Anzinger   george@xxxxxxxxxx
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/