[C#]SigScan help...

[abuckau907]

"Well what exactly is one to think when something is being put into something called IntPtr "

uh..seriously... unless you READ THE DATA from it..and that data is another ADDRESS..it's not a Pointer, it's just an address.

"Its value is added to a base value.. "

I didn't see any addition in your code...
xx = SigScan()
WriteBytes(xx)


?????? you probably do use offsets, but not in the code you posted (and that we're talking about)

[Cypher]

Well what exactly is one to think when something is being put into something called IntPtr. Pointer is in the GD name dude. It doesn't matter what the data being held actually represents... its called an IntegerPointer. Its pointing me to a specific spot in memory. The "offset" I'm getting, is subtracting whatever the base is, and wham... thats how far off of the start of the program I need to look for whatever I'm doing... its an offset.

Citation:
The distance from a starting point, either the start of a file or the start of a memory address. Its value is added to a base value to derive the actual value. An offset into a file is simply the character location within that file, usually starting with 0; thus "offset 240" is actually the 241st byte in the file. See relative address.
Offset Definition from PC Magazine Encyclopedia

#2: In computer engineering and low-level programming (such as assembly language), an offset usually denotes the number of address locations added to a base address in order to get to a specific absolute address. In this (original) meaning of offset, only the basic address unit, usually the 8-bit byte, is used to specify the offset's size. In this context an offset is sometimes called a relative address.
Offset (computer science) - Wikipedia, the free encyclopedia

So yes, I am using it properly.


And yes, you are nit picking with the way I used the words. All I'm doing is saying its returning an IntPtr... because it is. Thats the freaking data type being returned, into an IntPtr variable type.

You're replying to the wrong person champ. I didn't have anything to say about the definition of 'offset'. I was discussing the bolded part of the post I quoted (regarding natural numbers).

Unless your original 'grammar nazi' post wasn't directed at me to begin with? Upon a re-read of the thread it seems you were probably referring to abuckau907. If that's the case you need to utilize the 'quote' feature to make it clear who you're talking to.

[abuckau907]

only reason I started the 'technically integer/pointer/address' was because, the way he spoke, sounded like there was some addr/ptr confusion..
"It doesn't matter what the data being held actually represents... its called an IntegerPointer " -- true statement,
but unless it POINTS to something, don't call it a pointer, there is a huge difference --> you call it a pointer, we all assume there is an important address BEING STORED there.
You can call it IntPtr ALL DAY LONG and we'll know you mean 'an address'. When you call it a 'pointer' we assume there is data being stored at that address. I'm not being Nazi, that's just how it works :/

"[IntPtr]... Its pointing me to a specific spot in memory. " -- you can think of it this way, but that's not how the rest of us use 'points to'

[FattyXP]

I didn't call it a pointer dude. I called it an IntPtr. What am I suppose to type out half the variable type? I never once said I was reading anything, or anything of a sort. I said I'm getting an IntPtr returned from SigScan... exactly whats happening. I literally never put more than three letters of the word pointer in my GD post, all I said is I'm getting an IntPtr in return from SigScan.
And if you actually followed what I was talking about, I'm trying to use SigScan to find an address I ALREADY KNOW THE OFFSET OF(but I'm trying to make the code work through patches...). The resulting number in the IntPtr variable, subtracting the base, is resulting in that proper offset that I'm already using, so I know its finding the proper memory location? ****ing got it now? god.

[abuckau907]

I didn't call it a pointer dude. I called it an IntPtr.

" I literally never put more than three letters of the word pointer in my GD post"
" I have SigScan returning an IntPtr to pAddr. Then I am trying to pass that pointer to WriteBytes "

CALL IT A POINTER, and we assume you mean POINTER.
I'm not being nazi, you don't understand pointers. I was trying to help you.


1. SigScan works correctly
2. WriteBytes works correctly
3. Where is the problem?

[FattyXP]

" I literally never put more than three letters of the word pointer in my GD post"
" I have SigScan returning an IntPtr to pAddr. Then I am trying to pass that pointer to WriteBytes "

CALL IT A POINTER, and we assume you mean POINTER.
I'm not being nazi, you don't understand pointers. I was trying to help you.


1. SigScan works correctly
2. WriteBytes works correctly
3. Where is the problem?

Didn't realize I had said that, but anyways the problem was fixed. Was basing my work off of an incorrect sig and offset. It was modifying something I wasn't suppose to which immediately causes wow to crash. I wasn't re-testing the offset to make sure it was the proper one, and somehow before I started with the whole SigScan thing the offset got changed to one that wasn't correct, so when I fired up OllyDbg I was looking at the wrong location, and made a Sig to find that particular offset, which was wrong to begin with.

[abuckau907]

sweetness. yeah, i figured when you said wow was crashing, you were writing to the wrong address -- i did it quite a few times when trying to make a codecave and detour. Glad it's working.