Max a écrit :
Some questions about winedbg usability !
- Would it difficult to add an options (something like SHOWREGS=on/off) that allows to have regs displayed automatically after a breakpoint AND after a NEXTI command ? I find it painful to have to issue NEXTI and then INFO REGS each time.... remember old good ms-dos debugger !!! :-)
the best way would be to enhance the display functions with somethings like display $regs not difficult
2)- What about the possibility to set off-code breakpoints ? It happens often that I must set a break (in asm code) that is in a DLL which isn't already loaded... That gives a BAD ADRESS, of course. Borland debugger accepts the breakpoints and set it when the code gets loaded. Now the only way is to set breaks in dll-loading routine, wait up to the wanted dll gets loaded and then put the break... awful !
OTOH, it's also very awful to set a bp on memory which isn't mapped yet... you cannot write on it :-) anyway, we could do something like we do now for bp setting (expressed as a string) and automatically set the bp on DLL loading (if we can) rather easy (just follow what's done for deferred bp)
3)- And now the difficultest ! After solving the point 2, what about a way to store/retrieve breakpoints settings from disk ? Finding a bug in asm code often requires days (hmmm... nights !) of stepping, and a way to save breakpoints settings would spare tons of notes on paper :-)
that's a bit harder (especially, since we don't want the user to interact), but basically it's just setting the parser to read from a file stream instead of stdin
A+