I am going to put your reply in a special place, for the day I can
understand it :)
On Tue, Oct 17, 2017 at 2:37 AM, James Chapman wrote:
> We're heading into advanced territory here and I might get told off but...
> Consider this C++ program for a second, it has a struct with different
> types
cool stuff!
On Tue, Oct 17, 2017 at 2:17 AM, Alan Gauld via Tutor
wrote:
> On 17/10/17 01:02, Michael C wrote:
>
> > that is, one number, can be truncated and exist in multiple locations
> like
> > this
> >
> > double = 12345678
> >
> > 123 is at x001
> > 45 is at x005
> > 678 is at x010
>
> Tha
We're heading into advanced territory here and I might get told off but...
Consider this C++ program for a second, it has a struct with different
types of variables which sit next to each other in memory. When you print
the byte values of the struct, you can see that there is no easy way to
know wh
On 17/10/17 01:02, Michael C wrote:
> that is, one number, can be truncated and exist in multiple locations like
> this
>
> double = 12345678
>
> 123 is at x001
> 45 is at x005
> 678 is at x010
That won't happen, a single variable will always be in a a single
area.
But the representation won't
On 17/10/17 00:53, Michael C wrote:
> ah, i am bummed completely haha.
>
> Is there a way to tell which parts a variables so I can scan it?
> Maybe you could point me to some reading materials?
There are some rules about where programs store data within
their memory space, but typically that will
Hold on, supposed by using Openprocess and VirtualQueryEx, I have the
locations of all the memory the application is using, wouldn't this to be
true?
Say, a 8 byte data is somewhere in the region i am scanning. Ok, I know by
scanning it like this
for n in range(start,end,1)
will read into another
ah, i am bummed completely haha.
Is there a way to tell which parts a variables so I can scan it?
Maybe you could point me to some reading materials?
thanks :)
On Mon, Oct 16, 2017 at 4:48 PM, Alan Gauld via Tutor
wrote:
> On 16/10/17 21:04, Michael C wrote:
>
> > I don't understand this part
On Mon, Oct 16, 2017 at 01:04:40PM -0700, Michael C wrote:
> Hi all:
>
>
> I don't understand this part about the memory:
>
> if I used VirtualQueryEx to find out if a region of memory is ok to scan,
> and it
> says it's ok, are the values in the region arranged like this:
>
> short,int,double,
On 16/10/17 21:04, Michael C wrote:
> I don't understand this part about the memory:
And I'm not sure I understand your question but...
> if I used VirtualQueryEx to find out if a region of memory is ok to scan,
> and it
> says it's ok, are the values in the region arranged like this:
>
> short