Results 1 to 6 of 6

Thread: OllyDbg memory breakpoint management

  1. #1
    shERis
    Guest

    OllyDbg memory breakpoint management

    Hi!
    OllyDbg only has 2 ways to handle a memory exception:
    1. memory on access
    2. memory on write

    but there is no
    3. memory on execution

    I read, that there is a patched olly for point 3.
    Can anybody help me to get that patched version ?
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  2. #2
    Newbie_Cracker
    Guest

    OllyDbg memory breakpoint management

    Mem on access is similar to mem on execute...
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  3. #3

    OllyDbg memory breakpoint management

    Are you wrong, is not similar, BPM on access stop in execute and stop in read, and he need only stop in execute only, not read is very very different.

    In a packer you put a BPM ON ACCESS in the code section and OLLY stop each time write a value in the section (can stop 1000 or 2000 times before reach OEP), and with a BPM ON EXECUTE only OLLY stop in the OEP or the first line of the section executed is very different.

    I patch a olly for non stop in read and only on execute the problem in each time the program skip a possible stop for read take a little time, and for a complete unpacking can take 5 or 10 minutes for reach the oep, but you can take a coffe and return and OLLY will be waiting sttoped in OEP.

    Ah you need put all marks in debugging options-exceptions, and try in a previous RUN, the program skip all exceptions, for OLLY don´t stop in exceptions, and only in the BPM on EXECUTION.

    http://www.ricnar456.dyndns.org/HERRAMIENTAS/L-M-N-Ñ-O-P/OLLY%20PARCH EADO%20PARA%20BUSCAR%20OEPs.rar


    user and pass:hola

    And this OLLY never stop in BPM reads, for this use a common OLLY.

    This can be useful for VB programs you put a BPM on ACCESS in code and stop only when execute program and not the VB dll, jeje.

    Ricardo Narvaja

  4. #4
    shERis
    Guest

    OllyDbg memory breakpoint management

    Hi Ricardo!
    Thank you for your patched OllyDbg and for giving the link to me.
    It´s a great improvement!
    Do you have an idea why Olly didn´t implement a command "Memory Breakpoint on Execution" ?
    shERis
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  5. #5

    OllyDbg memory breakpoint management

    is not possible in RING3 always you have permission for execute, the read permision work togheter, only in RING 0 is possible separate BPM ON EXECUTION fron BPM ON READ.

    In my patched,if OLLY stop in read in BPM ON ACCESS, i patch to force to continue running, the effect is the same but only more slow, but works.

    Ricardo

  6. #6
    shERis
    Guest

    OllyDbg memory breakpoint management

    I assume that Olly didn´t want to implement that command, because your way of solving the problem is wasting much execution time and so OllyDbg would be very slowly. But it is good that you made it working.
    Thanx Ricardo!
    It´s fascinating for me what you know.
    I promise that I have read the FAQ and tried to use the Search to answer my question.

Similar Threads

  1. Pydbg and memory breakpoint
    By opc0d3 in forum The Newbie Forum
    Replies: 0
    Last Post: November 16th, 2012, 06:11
  2. unreproducible breakpoint (OllyDBG) and bad human memory!
    By WeapoNX2007 in forum OllyDbg Support Forums
    Replies: 4
    Last Post: July 15th, 2007, 09:38
  3. setting a memory breakpoint on priv
    By clafrieda in forum OllyDbg Support Forums
    Replies: 2
    Last Post: February 9th, 2006, 08:36
  4. how do you breakpoint on memory access?
    By FireRaven in forum OllyDbg Support Forums
    Replies: 4
    Last Post: April 11th, 2005, 10:05
  5. how to set breakpoint on memory range > 4 bytes
    By ddif in forum OllyDbg Support Forums
    Replies: 2
    Last Post: February 21st, 2004, 16:55

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •