This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Making "info thread" sane


George Anzinger wrote:
> The problem is that, for most threaded apps and for the kernel which
> treats each task as a thread, the "info thread" command gives a list
> of threads all stopped in the context switch code.  What is desired is
> to do one or more "up" commands and report info on this location.

Hi Everyone,

I just posted a couple patches (on gdb-patches) which I did to
support using kgdb on x86-64 linux.

The one titled "thread info - automatic skip frames" addresses
the problem George described above.  

My patch lets you list functions which should be automatically
skipped when choosing a frame to display as part of the 
"info threads" command.  e.g.:

	set skip-frame thread_return,schedule_timeout
	
Jim Houston - Concurrent Computer Corp.







Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]