Results 1 to 8 of 8

Thread: Unable to read memory of debugged program

  1. #1

    Unable to read memory of debugged program

    Hello,

    while debugging a program I recently downloaded I'm getting a "Unable to read memory of debugged program" error message on almost all commands available. Anyone have an idea on how this is accomplished?

    Regards,
    yaa

  2. #2

    Unable to read memory of debugged program

    Hello,

    if anyone wants to take a look at the program that is determining this behavior, this is Visual Prolog 6.1 and it can be downloaded from www.simtel.net/product.download.mirrors.php?id=60705.


    Regards,
    yaa

  3. #3
    Anonymous
    Guest

    Unable to read memory of debugged program

    If this is not your own program, then it's almost certainly because you trying to "crack" the program, which is not permitted to be talked about on this site.
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  4. #4

    Unable to read memory of debugged program

    Hello,

    I'm not trying to crack anything, the product is a freeware for personal use, so there is really no reason why one should crack it. I develop software myself and often debug programs to "take a look" at how others accomplish certain results expecially what apis are called and passing what parameters.

    Regards,
    yaa

  5. #5
    Anonymous
    Guest

    Unable to read memory of debugged program

    Hi,
    I have the same probs, but in this time its a crackme RECCXi (http://picasso.poupe.net/?p=recc).
    Can anybody help me?
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  6. #6
    Anonymous
    Guest

    Unable to read memory of debugged program

    Look up VirtualProtectEx?
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  7. #7
    Anonymous
    Guest

    Unable to read memory of debugged program

    I get the same error when trying to set a breakpoint on a WM message. I would like to be able to break when WM_COMMAND is sent to the application. In the OllyDbg help it explains how to do this but when I set the breakpoint this error appears.

    Thanks,
    Alex
    I promise that I have read the FAQ and tried to use the Search to answer my question.

  8. #8

    Unable to read memory of debugged program

    Ok, it seems that VirtualProtectEx could explain the behaviour we are seeing ... I'd guess that called with a PAGE_EXECUTE would probably be the right choice.

    In fact it would be nice to develop a tool that could "query" another process' virtual memory space and "draw" a map of that memory allowing to eventually change the setting of memory pages ...

    Does such a tool already exist?

    yaa

Similar Threads

  1. Break on memory read!
    By opc0d3 in forum Advanced Reversing and Programming
    Replies: 5
    Last Post: January 9th, 2013, 15:20
  2. How can I allocate memory in debugged program?
    By forgot in forum Plugins (General)
    Replies: 4
    Last Post: August 9th, 2005, 06:07
  3. Hardware-based read-only memory
    By disavowed in forum Advanced Reversing and Programming
    Replies: 6
    Last Post: January 12th, 2004, 21:57
  4. Conditional breakpoint on memory read access*
    By ollynewby in forum OllyDbg Support Forums
    Replies: 2
    Last Post: March 25th, 2003, 06:12
  5. Need program to read input
    By vgb in forum Tools of Our Trade (TOT) Messageboard
    Replies: 3
    Last Post: April 17th, 2002, 02:43

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
  •