public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* How can I explain for this? what is __kernel_vsyscall () ?
@ 2012-07-11 10:12 Tom Frank
  2012-07-11 10:38 ` Bjoern Doebel
  0 siblings, 1 reply; 2+ messages in thread
From: Tom Frank @ 2012-07-11 10:12 UTC (permalink / raw)
  To: gdb

I debug a multithreads  programme  with gdb,as it runs  I  use the
'info threads' command, and find that  most of the threads running at
__kernel_vsyscall () function

as below:

  6    Thread 0xb61e4b90 (LWP 322) 0x008e7402 in __kernel_vsyscall ()
  5    Thread 0xb6be5b90 (LWP 320) 0x008e7402 in __kernel_vsyscall ()
  4    Thread 0xb7fe7b90 (LWP 318) 0x008e7402 in __kernel_vsyscall ()
  3    Thread 0xb75e6b90 (LWP 316) 0x008e7402 in __kernel_vsyscall ()
* 1    Thread 0xb7fe86d0 (LWP 312) 0x0074c2b8 in clone () from
/lib/i686/nosegneg/libc.so.6



what is __kernel_vsyscall (),  why most threads's frame  is in that  step ?

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: How can I explain for this? what is __kernel_vsyscall () ?
  2012-07-11 10:12 How can I explain for this? what is __kernel_vsyscall () ? Tom Frank
@ 2012-07-11 10:38 ` Bjoern Doebel
  0 siblings, 0 replies; 2+ messages in thread
From: Bjoern Doebel @ 2012-07-11 10:38 UTC (permalink / raw)
  To: Tom Frank; +Cc: gdb

2012/7/11 Tom Frank <gdbhelper@gmail.com>:
> I debug a multithreads  programme  with gdb,as it runs  I  use the
> 'info threads' command, and find that  most of the threads running at
> __kernel_vsyscall () function
>
> as below:
>
>   6    Thread 0xb61e4b90 (LWP 322) 0x008e7402 in __kernel_vsyscall ()
>   5    Thread 0xb6be5b90 (LWP 320) 0x008e7402 in __kernel_vsyscall ()
>   4    Thread 0xb7fe7b90 (LWP 318) 0x008e7402 in __kernel_vsyscall ()
>   3    Thread 0xb75e6b90 (LWP 316) 0x008e7402 in __kernel_vsyscall ()
> * 1    Thread 0xb7fe86d0 (LWP 312) 0x0074c2b8 in clone () from
> /lib/i686/nosegneg/libc.so.6
>
>
>
> what is __kernel_vsyscall (),  why most threads's frame  is in that  step ?

__kernel_vsyscall() is Linux' system call entry point and the threads
you are looking at seem to be blocking in such a syscall. To find out
which it is, you might want to have a look at their EAX register
(assuming you're on x86).

Bjoern

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-07-11 10:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-11 10:12 How can I explain for this? what is __kernel_vsyscall () ? Tom Frank
2012-07-11 10:38 ` Bjoern Doebel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).