This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: problems with gdb multi-thread debugging and memset
- From: Daniel Jacobowitz <drow at false dot org>
- To: Booby Chen <pyghcb at 163 dot com>
- Cc: gdb <gdb at sources dot redhat dot com>
- Date: Tue, 3 Aug 2004 09:01:06 -0400
- Subject: Re: problems with gdb multi-thread debugging and memset
- References: <E1BrSxK-0006LW-00@return.false.org>
On Mon, Aug 02, 2004 at 10:52:15AM +0800, Booby Chen wrote:
> Hi all,
>
> when I use gdb to debug a multithread program like the following:
>
> (gdb) inf thr
> 4 Thread 2051 (LWP 14625) 0x420292e5 in sigsuspend () from /lib/i686/libc.so.6
> * 3 Thread 1026 (LWP 14624) sch_hd_core (arg=0x8ac60f8) at schrun.cpp:221
> 2 Thread 2049 (LWP 14623) 0x420e0037 in poll () from /lib/i686/libc.so.6
> 1 Thread 1024 (LWP 14619) 0x420b4b31 in nanosleep () from /lib/i686/libc.so.6
>
> (gdb) n
> 221 memset(&req4sch,0,sizeof(req4sch));
>
> and when I use the command "next", the thread 3 can not go on, but if I change the current
> thread to thread 4 and use the command "next", the thread 3 and 4 can go on.
>
> can anybody tell me the reason of this??Thanks.
What do you mean by "can not go on"?
--
Daniel Jacobowitz