public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "richard_sharman at mitel dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/18127] threads spawned by infcall end up stuck in "running" state Date: Tue, 05 May 2015 15:31:00 -0000 [thread overview] Message-ID: <bug-18127-4717-KdbhobnMVs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18127-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18127 Richard Sharman <richard_sharman at mitel dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard_sharman at mitel dot com --- Comment #1 from Richard Sharman <richard_sharman at mitel dot com> --- I have seen something similar: when stopped at a breakpoint printing a variable that has a [python] pretty printer (and scheduler-locking is off) quite often other threads run before the printing is finished, and if any of these threads create other threads then these newly created threads -- and, for some reason some existing threads -- appear as running. The following shows a normal "into thread" with all threads stopped, but after the print msg [a structure that contains a field that is pretty printed] the info threads shows many threads running, and not just the new ones. At this point we cannot continue. (gdb) c Continuing. [New Thread 0xf70e3930 (LWP 7456)] [Switching to Thread 0xf71a67b0 (LWP 7427)] Breakpoint 1, ccsend (msg=...) at cgen/message0.cc:498 (gdb) info thread Id Target Id Frame 19 Thread 0xf70e3930 (LWP 7456) "McastAudit" 0xf7ffd430 in __kernel_vsyscall () 18 Thread 0xf7105930 (LWP 7452) "McastAudit" 0xf7ffd430 in __kernel_vsyscall () 17 Thread 0xf70ed7b0 (LWP 7453) "auditmgr " 0xf7ffd430 in __kernel_vsyscall () 16 Thread 0xf7134930 (LWP 7451) "McastAudit" 0xf7ffd430 in __kernel_vsyscall () 15 Thread 0xf078d7b0 (LWP 7447) "debug_term " 0xf7ffd430 in __kernel_vsyscall () 14 Thread 0xf71527b0 (LWP 7448) "auditwork " 0xf7ffd430 in __kernel_vsyscall () 13 Thread 0xf7148930 (LWP 7449) "tSsuSrvHS" 0x0072b505 in dl_open_worker () from /lib/ld-linux.so.2 12 Thread 0xf713e930 (LWP 7450) "McastAudit" 0xf7ffd430 in __kernel_vsyscall () 11 Thread 0xf07977b0 (LWP 7446) "maint_term " 0xf7ffd430 in __kernel_vsyscall () 10 Thread 0xf7ffa7b0 (LWP 7441) "dbgmtterm " 0xf7ffd430 in __kernel_vsyscall () 9 Thread 0xf719c7b0 (LWP 7442) "cmsgsysin " 0xf7ffd430 in __kernel_vsyscall () 8 Thread 0xf71667b0 (LWP 7443) "auditmgr " 0xf7ffd430 in __kernel_vsyscall () 7 Thread 0xf715c930 (LWP 7444) "tMainApplQ" 0xf7ffd430 in __kernel_vsyscall () 6 Thread 0xf13bc7b0 (LWP 7423) "dispatch " 0xf7ffd430 in __kernel_vsyscall () 5 Thread 0xf7ff07b0 (LWP 7424) "msgtimer " DynArray<Array<unsigned short, 0, 3> >::operator[] ( this=0x99f2c46 <msgtimer_allocation>, index=4262) at /home/gx5000/sharman/mpascaldir/d08/x86-linux/Array.h:180 4 Thread 0xf7fe67b0 (LWP 7425) "guardian " 0xf7ffd430 in __kernel_vsyscall () 3 Thread 0xf71b07b0 (LWP 7426) "cleanup " 0xf7ffd430 in __kernel_vsyscall () * 2 Thread 0xf71a67b0 (LWP 7427) "sysinit " ccsend (msg=...) at cgen/message0.cc:498 1 Thread 0xf7741a30 (LWP 7412) "cc" 0xf7ffd430 in __kernel_vsyscall () (gdb) p msg $4 = (message &) @0xf71a5a3a: {control_byte = {msg_type = reg_msg, redun = {sdrd = plane_0, rxrd = plane_0}}, tx_node = { group = 0 '\000', level = maincpu, {{subsystem_id = message_switch, upper_id_byte = 0 '\000', lower_id_byte = 0 '\000'}, { cntrlr_no = 0 '\000', card_no = 0 '\000', circuit_no = 0 '\000'}}}, rx_node = {group = 0 '\000', level = maincpu, {{ subsystem_id = message_switch, upper_id_byte = 0 '\000', lower_id_byte = 0 '\000'}, {cntrlr_no = 0 '\000', card_no = 0 '\000', circuit_no = 0 '\000'}}}, enter_lld_when_received = 0 '\000', [New Thread 0xf70d9930 (LWP 7457)] tx_sw = 0x70006 (7,6) "sysinit ", [New Thread 0xf70c5930 (LWP 7459)] [New Thread 0xf70cf930 (LWP 7458)] rx_sw = 0x7000d (7,13) "auditmgr ", tx_applic_id = nil_applic, function_code = 13 '\r', data = {storage = "\002", '\000' <repeats 18 times>}, checksum = 0 '\000', icb = 0 '\000'} (gdb) info thread Id Target Id Frame 22 Thread 0xf70cf930 (LWP 7458) "McastAudit" 0xf7ffd430 in __kernel_vsyscall () 21 Thread 0xf70c5930 (LWP 7459) "SsuPeerSrvI" 0xf7ffd430 in __kernel_vsyscall () 20 Thread 0xf70d9930 (LWP 7457) "McastAudit" (running) 19 Thread 0xf70e3930 (LWP 7456) "McastAudit" (running) 18 Thread 0xf7105930 (LWP 7452) "McastAudit" (running) 17 Thread 0xf70ed7b0 (LWP 7453) "auditmgr " (running) 16 Thread 0xf7134930 (LWP 7451) "McastAudit" (running) 15 Thread 0xf078d7b0 (LWP 7447) "debug_term " (running) 14 Thread 0xf71527b0 (LWP 7448) "auditwork " (running) 13 Thread 0xf7148930 (LWP 7449) "tSsuSrvHS" (running) 12 Thread 0xf713e930 (LWP 7450) "McastAudit" (running) 11 Thread 0xf07977b0 (LWP 7446) "maint_term " (running) 10 Thread 0xf7ffa7b0 (LWP 7441) "dbgmtterm " (running) 9 Thread 0xf719c7b0 (LWP 7442) "cmsgsysin " (running) 8 Thread 0xf71667b0 (LWP 7443) "auditmgr " (running) 7 Thread 0xf715c930 (LWP 7444) "tMainApplQ" (running) 6 Thread 0xf13bc7b0 (LWP 7423) "dispatch " (running) 5 Thread 0xf7ff07b0 (LWP 7424) "msgtimer " (running) 4 Thread 0xf7fe67b0 (LWP 7425) "guardian " (running) 3 Thread 0xf71b07b0 (LWP 7426) "cleanup " (running) * 2 Thread 0xf71a67b0 (LWP 7427) "sysinit " (running) 1 Thread 0xf7741a30 (LWP 7412) "cc" (running) (gdb) c Continuing. Cannot execute this command while the selected thread is running. (gdb) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-05-05 15:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-15 7:56 [Bug threads/18127] New: " palves at redhat dot com 2015-05-05 15:31 ` richard_sharman at mitel dot com [this message] 2015-05-05 17:07 ` [Bug threads/18127] " palves at redhat dot com 2015-05-05 18:05 ` richard.sharman at mitel dot com 2015-06-10 15:33 ` eliz at gnu dot org 2015-06-29 15:55 ` cvs-commit at gcc dot gnu.org 2015-06-29 18:58 ` palves at redhat dot com
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=bug-18127-4717-KdbhobnMVs@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).