From: "Booby Chen" <pyghcb@163.com>
To: "gdb" <gdb@sources.redhat.com>
Subject: problems with gdb multi-thread debugging and memset
Date: Mon, 02 Aug 2004 02:52:00 -0000 [thread overview]
Message-ID: <20040802025200.tYLcECVOxXlf75G3_s3s0dkavtN46yEl0ASJaOBUrqI@z> (raw)
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.
Regards,
Booby Chen
next reply other threads:[~2004-08-02 2:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 2:52 Booby Chen [this message]
[not found] <E1BrSxK-0006LW-00@return.false.org>
2004-08-03 13:02 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
2004-08-02 2:52 Booby Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040802025200.tYLcECVOxXlf75G3_s3s0dkavtN46yEl0ASJaOBUrqI@z \
--to=pyghcb@163.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox