hi all,
Olly plans to have a help rewrite and needs your opinion of what
should be in it, how to be structured, do you need a tutorial, ....
feel free to post your ideeas.
i betatest 1.08 - groovy:
- code highlighting (push/pop one colour,calls another color)
- CodeView support (see your asm source inside CPU window) :alright:
- heap walk (not available on NT systems :()
Olly plans to have a help rewrite and needs your opinion of what
should be in it, how to be structured, do you need a tutorial, ....
feel free to post your ideeas.
i betatest 1.08 - groovy:
- code highlighting (push/pop one colour,calls another color)
- CodeView support (see your asm source inside CPU window) :alright:
- heap walk (not available on NT systems :()
Two things that would make me think more about using Olly....
1. More than 1 memory window (maybe it has that now?)
2. Use my Desktop colors, or custom colors besides the NEON ones you can use now.
1. More than 1 memory window (maybe it has that now?)
2. Use my Desktop colors, or custom colors besides the NEON ones you can use now.
1. More than 1 memory window (maybe it has that now?)
ALT+M, select address range, right click, DUMP (CTRL+G - go address)
Use my Desktop colors, or custom colors besides the NEON ones you can use now.
you can create your own color scheme (with realtime preview)
in Options/Appearance/Colours
anything else ? :)
you can create your own color scheme (with realtime preview)
in Options/Appearance/Colours
Problem is it seems I cannot select any color except the 20 default colors. None of which I'd actually use because they are all too saturated.
When you're typing a instruction, it would be nice to be able to preview the number of bytes it assembles to.
And perhaps the tracing of multiple threads could be improved?
Also, when will version 1.08 be available? Sounds like something I simply must have :alright:
And perhaps the tracing of multiple threads could be improved?
Also, when will version 1.08 be available? Sounds like something I simply must have :alright:
Would like to see my code as I wrote it and be able to put a break point
on any line of my code. Don't care about disassembling the code.
Be able to enter a label and branch directly to it.
on any line of my code. Don't care about disassembling the code.
Be able to enter a label and branch directly to it.
It would be nice to have support for the source code in Masm also. I think Olly supports Tasm only, currently.
Rudy.
Rudy.
perhaps this is already possible, but i couldn't
get it to work....
i want to set a breakpoint (with F2) ... then Run to that
breakpoint.... so far, so good..i can do that
...but then i want to set another bp further on in the code
and resume execution from the 1st bp. i can single step (with F7)
...but can you resume RUN from the 1st bp ?
get it to work....
i want to set a breakpoint (with F2) ... then Run to that
breakpoint.... so far, so good..i can do that
...but then i want to set another bp further on in the code
and resume execution from the 1st bp. i can single step (with F7)
...but can you resume RUN from the 1st bp ?
Integrate it with an assembler and a editor, and make it become a source-level debugger.
Like Asm-One for Amiga, IMO the very best (by far) assembler I've ever used. If you have an Amiga emulator I will send you a copy of it to take a look to. I think the PC needs++ such a product.
Like Asm-One for Amiga, IMO the very best (by far) assembler I've ever used. If you have an Amiga emulator I will send you a copy of it to take a look to. I think the PC needs++ such a product.
It would be nice to have an API hooker/breakpointer integrated (maybe as a plug-in?).
...but can you resume RUN from the 1st bp?
thanks, bitrake...
... that'll save me a lot of fiddling around...:cool:
... that'll save me a lot of fiddling around...:cool:
ThoughtCriminal: i will put color change on wish list, but it is low priority
Qweerdy: what do you mean by "tracing of multiple threads could be improved" ?
a bit more specific please. preview the number of bytes added to wish list
shankle: OllyDbg is a disassembler/debugger not a compiler ... but you are free to
make one as you like, Olly post his 1 line assembler/disassembler engine on his homepage
Rudy Penteado: 1.08 will support it :alright: ... i play with right now and it's great
Maverick: this need a whole rewrite ... but i think a plugin for the IDEs would help
toward that direction. can you PM me to talk about ?
comrade: plugin APi is available ... go and write one plugin :grin: ... you can use
cmdline line plugin as skeleton
thanks all and w8ing for your replies
Qweerdy: what do you mean by "tracing of multiple threads could be improved" ?
a bit more specific please. preview the number of bytes added to wish list
shankle: OllyDbg is a disassembler/debugger not a compiler ... but you are free to
make one as you like, Olly post his 1 line assembler/disassembler engine on his homepage
Rudy Penteado: 1.08 will support it :alright: ... i play with right now and it's great
Maverick: this need a whole rewrite ... but i think a plugin for the IDEs would help
toward that direction. can you PM me to talk about ?
comrade: plugin APi is available ... go and write one plugin :grin: ... you can use
cmdline line plugin as skeleton
thanks all and w8ing for your replies
Is there a way to import a symbol table. For me it's a two sided problem since FAsm doesn't export a symbol table, but that my change.
Secondly, could an option be added to all the working directory be inherited from the process that started Ollydbg, and not the directory of the debugged program?
Third, I would love a color definitions file. That way I could match the colors of the mnemonics to what I use with textpad.
Fourth, can ollydbg remember the location of all the separating lines.
Finally, I've noticed that I have to left click on a line in the memory map before I can dump it. Can that be change so that a right click would suffice. Also, could a key be associated with dump, maybe enter.
Maverick:
TextPad does a pretty good job of integrating utilities. My setup comprises Ctrl-F7 to assemble, then Ctrl-Shft-F7 to debug; I could even create icons for the job. I think with support for symbols, it would be a fairly complete IDE.
Secondly, could an option be added to all the working directory be inherited from the process that started Ollydbg, and not the directory of the debugged program?
Third, I would love a color definitions file. That way I could match the colors of the mnemonics to what I use with textpad.
Fourth, can ollydbg remember the location of all the separating lines.
Finally, I've noticed that I have to left click on a line in the memory map before I can dump it. Can that be change so that a right click would suffice. Also, could a key be associated with dump, maybe enter.
Maverick:
TextPad does a pretty good job of integrating utilities. My setup comprises Ctrl-F7 to assemble, then Ctrl-Shft-F7 to debug; I could even create icons for the job. I think with support for symbols, it would be a fairly complete IDE.
eet_1024: you can import symbols by using a plugin that i made that
get IDA symbols and insert them in OllyDbg. i will post it here tomorrow (dont have
here with me)
"color definitions file" = highlighting, will be available in 1.08 - looks nice
btw, i need some good looking schemes - if someone can make them i would
appreciate (screeshot of CPU dump and color it in graphics program would be nice
to have a quick look)
other ones added to wish list - will see if Olly thinks fits to implement them
get IDA symbols and insert them in OllyDbg. i will post it here tomorrow (dont have
here with me)
"color definitions file" = highlighting, will be available in 1.08 - looks nice
btw, i need some good looking schemes - if someone can make them i would
appreciate (screeshot of CPU dump and color it in graphics program would be nice
to have a quick look)
other ones added to wish list - will see if Olly thinks fits to implement them
Hi TBD: sure.. PM'ing you. I know it would cost a major rewrite, but if you tested throughly AsmOne you may fall in love with it and decide to turn OllyDbg into something similar, whatever is the work cost involved.
I hope other AsmOne users here may testimony about the quality of this integrated editor/debugger/monitor/assembler/disassembler/coffee_machine. :tongue:
Hi eet_1024: AsmOne gets its power mostly from the seamless, powerful and robust integration. I can't judge TextPad as you configured it because I haven't tested it, but I can advice you to install WinUAE and try AsmOne, since it's a source of very good ideas (including the editor). It's many little details that make it a great integrated assembler (just to name two, but these are unimportant among others, and are meant just as example: 1) in the editor you mark a region of text, and among the many functions there's one that tells you which CPU registers are used.. quite handy at times 2) the source level debugger starts in a istant and you get the current instruction highlighted in your source, plus a lot of (configurable on the fly) info on the bottom window, etc..). Really, it has to be seen/used to understand how good it is. Pity it is for 680x0. It has been the biggest source of inspiration for my own language's integrated-editor/compiler/debugger, that I still haven't found the time to finish tho. :(
Job kills.
I hope other AsmOne users here may testimony about the quality of this integrated editor/debugger/monitor/assembler/disassembler/coffee_machine. :tongue:
Hi eet_1024: AsmOne gets its power mostly from the seamless, powerful and robust integration. I can't judge TextPad as you configured it because I haven't tested it, but I can advice you to install WinUAE and try AsmOne, since it's a source of very good ideas (including the editor). It's many little details that make it a great integrated assembler (just to name two, but these are unimportant among others, and are meant just as example: 1) in the editor you mark a region of text, and among the many functions there's one that tells you which CPU registers are used.. quite handy at times 2) the source level debugger starts in a istant and you get the current instruction highlighted in your source, plus a lot of (configurable on the fly) info on the bottom window, etc..). Really, it has to be seen/used to understand how good it is. Pity it is for 680x0. It has been the biggest source of inspiration for my own language's integrated-editor/compiler/debugger, that I still haven't found the time to finish tho. :(
Job kills.
looking forward for the new version :)
what i'm also missing is the always on top function for the mdi windows.. it's pretty annoying to have the CPU window open and you want to open the breakpoints window with ALT+B, the CPU window minimizes and the breakpoint window pops up.
i tried to make a plugin for this but i couldnt get the windowhandles of the windows easily :)
just adding an "always on top" menu item in each MDI's system icon would be nice
what i'm also missing is the always on top function for the mdi windows.. it's pretty annoying to have the CPU window open and you want to open the breakpoints window with ALT+B, the CPU window minimizes and the breakpoint window pops up.
i tried to make a plugin for this but i couldnt get the windowhandles of the windows easily :)
just adding an "always on top" menu item in each MDI's system icon would be nice
here is a screenshot of 1.08 version
(1) highlight in action
(2) MASM32 source line
my layout is 80% CPU, and on lower 20% i have Breakpoints, Call stack and
Log data (for conditional breakpoints). this way i have everything that i need
in one screen. for anything else i use keyboard shortcuts/toolbar icons (E, M, W, ...)
(1) highlight in action
(2) MASM32 source line
my layout is 80% CPU, and on lower 20% i have Breakpoints, Call stack and
Log data (for conditional breakpoints). this way i have everything that i need
in one screen. for anything else i use keyboard shortcuts/toolbar icons (E, M, W, ...)
here is a screenshot of 1.08 version
(1) highlight in action
(2) MASM32 source line
my layout is 80% CPU, and on lower 20% i have Breakpoints, Call stack and
Log data (for conditional breakpoints). this way i have everything that i need
in one screen. for anything else i use keyboard shortcuts/toolbar icons (E, M, W, ...)
i guess that fixes my problem then :)
looks awesome! :alright:
Maverick, i downloaded WinUAE and AsmOne v147, and managed to download a kick.rom (kickstart 3.1) but how do i run it? when i load up the emulator i only get AmigaDOS :eek: