Hello,

recently while debugging a program I noticed a weird thing done by OD 1.09 and that is interpreting a opcodes inside a code segment as it they where data. I had to remove the analysis to get the opcodes to be interpreted correctly. Does anyone have any suggestion on what can be done in this cases?

H.

Hi,

I've got same problem debugging a program I wrote using win32asm. The problem was that I used a weird way for sniffers&crackers, so I included some strings inside the code, and the analyzer is not working properly with some opcodes (usually 'call'). I used some tips like:

Call MyMessageBox
DB 'Title',0,'Message,0

On MyMessageBox I use the "ret" address in the stack to get the offset for the strings... But the analyzers doesn't faults on this call, but in other in linear code snippet uses to show some opcodes as data (grayed).

The program is about 100ks os source code, and the compiled exe is about 20ks, so I could send it to Olly to find where is the problem with OllyDbg.