This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu, Jul 11, 2002 at 05:58:56PM -0500, Grant Edwards wrote: > I've noticed that gdb uses all the CPU it can get while the > target is running (e.g. busy-waiting 'till target stops). > > I'm building 5.2 to see if it still does that Yup. Here's a patch that fixes it. I only added the usleep() when there's no ui_loop_hook to call. Is that the right thing to do, or will Insight et al still suck CPU time? I'm not sure who's supposed to be surrendering the CPU, the UI or the target. Is usleep() portable? -- Grant Edwards grante@visi.com
Attachment:
rdi-busy-wait.patch
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |