This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/15853] New: 'thread apply all inetrrupt&' shows inefficiency on remote targets
- From: "mbilal at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 19 Aug 2013 11:35:42 +0000
- Subject: [Bug gdb/15853] New: 'thread apply all inetrrupt&' shows inefficiency on remote targets
- Auto-submitted: auto-generated
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.