Re: Two Click disassembly/reassembly

"Alex McDonald" <alex_mcd@xxxxxxxxxxxxxxx> écrivait
news:1138355729.219465.210770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

> 1. You would need to analyse the entire code, not just this fragment,
> to guarantee that someCodePtr is never modified.


Ah!... A MASM victim, here.

:)

Betov.

< http://rosasm.org >




.

Relevant Pages

  • Re: Two Click disassembly/reassembly
    ... You would need to analyse the entire code, not just this fragment, ... >> to guarantee that someCodePtr is never modified. ...
    (alt.lang.asm)
  • Re: Two Click disassembly/reassembly
    ... You would need to analyse the entire code, not just this fragment, ... >>> to guarantee that someCodePtr is never modified. ... How does the type of assembler change ...
    (alt.lang.asm)
  • Re: Two Click disassembly/reassembly
    ... > Betov wrote: ... >>> to guarantee that someCodePtr is never modified. ... you mean that you are not a MASM victim? ...
    (alt.lang.asm)
  • Re: atomicity of reads and writes in ntfs
    ... What you are observing is hardware & driver dependent behaviour - there is ... no guarantee that this behaviour will hold agnostically. ... write operations on NTFS files. ... If my target file is in one complete fragment then the ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Two Click disassembly/reassembly
    ... >> Betov wrote: ... you mean that you are not a MASM victim? ... Alex McDonald ...
    (alt.lang.asm)