From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1754 invoked by alias); 19 Aug 2013 11:35:43 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 1727 invoked by uid 48); 19 Aug 2013 11:35:42 -0000 From: "mbilal at codesourcery dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/15853] New: 'thread apply all inetrrupt&' shows inefficiency on remote targets Date: Mon, 19 Aug 2013 11:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mbilal at codesourcery dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-q3/txt/msg00230.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=15853 Bug ID: 15853 Summary: 'thread apply all inetrrupt&' shows inefficiency on remote targets Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mbilal at codesourcery dot com In the case of 'interrupt -a&' command gdb sends only one packet to stop all threads as $vCont;t#b9... But in case of 'thread apply all interrupt&' GDB issues indiviual packets for each thread.I think that In non-stop mode 'interrupt -a&' and 'thread apply all interrupt&' commands all equals but time efficiency of later command is less. Also. If user issues a command like 'thread apply all interrupt -a&' GDB accepts it and GDB will stop all threads on first vcount;t packets but due to loops, it sends vcount;t packet for all remaining threads altought gdb has already stop all thread so IMO it is a bug. -- You are receiving this mail because: You are on the CC list for the bug.