1 Jan 2007 05:16
Re: [PATCH] MI: new timing command
Nick Roberts <nickrob <at> snap.net.nz>
2007-01-01 04:16:00 GMT
2007-01-01 04:16:00 GMT
> > + Toggle the printing of the wallclock, user and system times for an MI > > + command as a field in its output. Â,A (BThis command is to help frontend > > + developers optimize the performance of their code. Â,A (B > > I though it's to help gdb developers to optimize performance of > their codeI was thinking of frontend developers as gdb developers would presumably use profiling but, hey, I'm making it up as I go along and if it proves useful for developing GDB too we can add that. > At least when gdb takes a second for list frames, > there's nothing I can do in a frontend
Well, for example, you can see the time that a command like -stack-list-frames takes and decide whether to cap the number of frames and what time that saves. > > No argument is > > + equivalent to <at> samp{yes}. > > I'd suggest to say that this command may return error if > timing is not available. Otherwise, frontend authors might > not even think this command can fail, and when it fails, > user will see completely buffling error message. Yes, I'll add this if I get approval for getrusage. -- -- Nick http://www.inet.net.nz/~nickrob
I was thinking of frontend developers as gdb developers would presumably use
profiling but, hey, I'm making it up as I go along and if it proves useful
for developing GDB too we can add that.
> At least when gdb takes a second for list frames,
> there's nothing I can do in a frontend
RSS Feed