windbg.info
Home Search
 You are here: arrow Home Forum

Search Our Site

www.windbg.info
Welcome, Guest
Please Login or Register.    Lost Password?
Memory Searching issue (command s)
(1 viewing) 1 Guest
Go to bottom
TOPIC: Memory Searching issue (command s)
#68
Brett K (User)
Posts: 4
User Offline

Memory Searching issue (command s) 31 May 2010 - 00:43
Hello! When I try to use the 's' command to search memory, it was coming up with no results. Upon dumping the memory region where I knew the byte-sequence I was looking for is located, the memory there was showing up as '???' a bunch of question marks. So I used the .pagein extension to page in that memory, and then it showed up. At this point, if I used the 's' command again, it would now find the byte-sequence. The problem I am having is, the images I debug are large (often 5-10mb), and they seem to get paged out all the time, making searching impossible. If I didn't know the exact address of where to find my byte-sequence, I wouldn't know which of the several thousand pages I'd need to .pagein to find it. So my question is, is there a way to prevent memory from being paged out, or a way to .pagein an entire executable image?
 
  Logged IP
  The administrator has disabled public write access.
Go to top
  up top of page up  
 

Copyright © 2024 WinDbg.info. All Rights Reserved.
Page generated in 0.0005 seconds.