This is the mail archive of the gdb-patches@sourceware.org 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]

Re: [PATCH 1/4] Fix dprintf bugs

On 03/07/2013 10:48 PM, Marc Khouzam wrote: 
So, I'm suggesting that sending an MI event from GDB to the frontend for
every dprintf hit is too much.  Does the same argument hold for async
remote notifications?  For efficiency, I'm thinking that agent dprintf should
not report every hit to GDB; instead, when GDB wants to know the hit
count (e.g, because of a -break-list command), it would ask the agent
for the current hit count.  This would cut down on the communication
from agent to GDB when using dprintf.

If we use async remote notification for hit count update, of course, GDBserver can't report *every* hit count update to GDB, which is relatively expensive. GDBserver shouldn't send new async remote notification to GDB until the previous notification is ack'ed by GDB.

--
Yao (éå)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]