I have a .exe which loads with a large part of its address space (~401000 - 600000) blank, and classed as .text. During initialization it loads code into that area and then executes from it. But Olly still considers it as a non-code area (the 'Contains' column in the Memory Map window is blank), so I can't get it displayed in the Disassembler pane of the CPU window and set execution breakpoints etc.

I presume that this can actually be done, I just can't figure out how. Can someone give me a few pointers, please?

Regards,

Change the characteristics of that section to code in the executable itself, Ollydbg should then disassemble it

take into account if its protected chances are you are going to run into integrity check problems by doing as 1bitshort suggests though.

Yes, thanks garryw, what I really want to do is to be able to tell Olly that the section is *now* (i.e. when I break at a time when the code has been loaded there) a code section.

I'm 2 days new to Olly, and quite like it. I would have thought that it would be a reasonably simple thing for Olly to be told to view address regions in different manners. Obviously there are considerations/dangers in treating sections in differing manners, but if the user is aware of the implications and is willing to accept the consequences, then so be it - software shouldn't prohibit you from doing something, even if it seems to be dangerous. Warnings, yes, even multiple warnings, but if the user really wants to do something, well...

Regards