Crono
October 26th, 2003, 04:49
Hi, i started (from 0) to use ollydbg some weeks ago for "educational purposes" (i'm not joking, i really needed it at the uni 
), and i loved it. Although debuggers are (imho) primarly used from the mass to crack programs, i found it useful to debug some c programs, and to learn how some compilers work. I also did many "crackme", and i think they're great to learn things.
However i think that ollydbg has 1-2 "workflow" limitations, and i'm here to ask you some help (maybe i only missed some things in the options dialog
)
One is the "feature" that sometimes disables breakpoints when you ctrl-f2 (restart). Why it does that? Is there a way to disable this thing?
Two is the keybindings. I'm very disappointed with the way keys are associated to actions: why every key opens the "assemble" (or comment ecc) dialog? I mean, i'm in a debugger, primarly i'm searching for things, settings breakpoints, reading memory... wouldn't be better to bind, for example, the B key to the breakpoints window, and to close it when it's open? I mean, if i want to see breakpoint now i have to use the mouse to click on the blue button, or press ALT-B (a bit tricky..), and to close it i have to press CTRL-F4 (argh!) or use the mouse. Imho, it would be better to have B open the bp win, and B to close it. And so on for other things (like CTRL-N, CTRL-E). When i debug a program i almost never modify the assembly code, in fact now i use the open comment dialog just 'cause sometimes i put comments on the code... i think that a "A" key that acts like a double click on the asm code would be better.
Or am i only saying stupidities?
However, thanks for this great app, it's the best and it's free.
), and i loved it. Although debuggers are (imho) primarly used from the mass to crack programs, i found it useful to debug some c programs, and to learn how some compilers work. I also did many "crackme", and i think they're great to learn things.However i think that ollydbg has 1-2 "workflow" limitations, and i'm here to ask you some help (maybe i only missed some things in the options dialog
)One is the "feature" that sometimes disables breakpoints when you ctrl-f2 (restart). Why it does that? Is there a way to disable this thing?
Two is the keybindings. I'm very disappointed with the way keys are associated to actions: why every key opens the "assemble" (or comment ecc) dialog? I mean, i'm in a debugger, primarly i'm searching for things, settings breakpoints, reading memory... wouldn't be better to bind, for example, the B key to the breakpoints window, and to close it when it's open? I mean, if i want to see breakpoint now i have to use the mouse to click on the blue button, or press ALT-B (a bit tricky..), and to close it i have to press CTRL-F4 (argh!) or use the mouse. Imho, it would be better to have B open the bp win, and B to close it. And so on for other things (like CTRL-N, CTRL-E). When i debug a program i almost never modify the assembly code, in fact now i use the open comment dialog just 'cause sometimes i put comments on the code... i think that a "A" key that acts like a double click on the asm code would be better.
Or am i only saying stupidities?
However, thanks for this great app, it's the best and it's free.