Welcome to the new Woodmann RCE Messageboards Regroupment
Please be patient while the rest of the site is restored.

To all Members of the old RCE Forums:
In order to log in, it will be necessary to reset your forum login password ("I forgot my password") using the original email address you registered with. You will be sent an email with a link to reset your password for that member account.

The old vBulletin forum was converted to phpBB format, requiring the passwords to be reset. If this is a problem for some because of a forgotten email address, please feel free to re-register with a new username. We are happy to welcome old and new members back to the forums! Thanks.

All new accounts are manually activated before you can post. Any questions can be PM'ed to Kayaker.

values of C variables shown as their addreses

Found a bug in OllyDbg? Post a report here.
Locked
fycom

values of C variables shown as their addreses

Post by fycom »

The watch window doesn't show values of C variables, but only their memory addresses... For integers the brackets can be used, but what with strings?....

Besides, it seems very annoying when the window focus switches to the code panel each time I step over CPU instructions :-(

Hmm.... in general I woud say that OllyDbg pays too many attention to CPU code analysis while the source file debugging is no less important (at least for me).
focht

values of C variables shown as their addreses

Post by focht »


Hmm.... in general I woud say that OllyDbg pays too many attention to CPU code analysis while the source file debugging is no less important (at least for me).


Agreed.
If you have emphasis on source level debugging, you should use a decent IDE with integrated debugger.
My fav is the VC++ debugger (integrated with VS.NET 2003/2005 IDE) along with VC++ compiler.

Regards
fycom

values of C variables shown as their addreses

Post by fycom »

Every source level debugger must have ability of CPU code analysis just because of program optimization. So I do not see here a good reason to cut debugging from reverse engineering tool. And I really think that it wouldn't be so difficult to add some enhancements to make OllyDbg to overcome in both these applications.

Concerning IDE. Integrated tools are too superfluous for what I really need. Because my need (and preference of life style) is to have a collection of constructive blocks from which I could create my own "integrated environment" specialized on my personal needs and preferences. I want to have a chance to use my favorite source editor, compiler, resource editor, debugger and whatever other thing I want.

I like freedom. Any monopoly (like IDE) takes it away from you.
fycom

values of C variables shown as their addreses

Post by fycom »

Now I found a good alternative for Borland's Turbo Debugger.
It is a stand alone source level debugger from Microsoft - WinDbg.exe.

If someone else needs it too, you can download it from here: http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.3.17.0. exe
Locked