How to call assemble code

I get machine code for the function:

Code:

---

void ptr()
{
  printf("Hello");
}

---

and I want to call them in another program,
Look:

Code:

---

typedef void (*PF)();
unsigned char buff[]="\x55\x89\xe5\x83\xec\x08\xc7\x04\x24\x50\x85\x04\x08\xe8\x02\xff\xff\xff\xc9\xc3";
int main(void)
{
 
  PF pf=(PF)buff
  pf();
  return 0;
}

---

but it always display Segmentation fault,
how to call the code?

Note that buff[] is a char array while pf is a pointer to a function returning void - the two are mutually exclusive.

The first general assumption is that someone who posts code as hex strings is trying some kind of code injection hackery.

The second general assumption is that such code is completely incompatible with the OS you're trying to run it on. For example, if that's 16-bit DOS code, then you're S-o-L if you're trying to run it on Linux.

The third general assumption is that your OS protects against executing code which isn't in a read-only-executable segment. Random hex like that is at best read-only, and certainly never executable.

So, please disassemble the code so we can see what you're up to.

It's probably worth reading the forum rules at this point before you go any further.

You say the code implements printf("Hello"), but it doesn't contain the proper ascii codes ....

Quote:

---

Originally Posted by oogabooga

You say the code implements printf("Hello"), but it doesn't contain the proper ascii codes ....

---

Even if it did have the right ascii codes, it wouldn't work on *nix machines (dunno about windoze) because on *nix only the text segment is executable, while buff[] lies in the data segment.

I imagine that Windows works the same as eunuchs in that way. My point was that his code is not implementing what he said it was.

Assuming its correct and meant to be 32-bit x86, it disassembles to:

Code:

---

push    ebp
mov    ebp, esp
sub    esp, 8
mov    dword ptr [eax+ecx], 0xFFFF02E8
dec    ecx
retn

---

Me neither

Judging by similar code on Wiki:

push ebp ; save calling function's stack frame (ebp)
mov ebp, esp ; make a new stack frame on top of our caller's stack
sub esp, 8 ; allocate 8 bytes of stack space for this function's local variables

and the next bits appear to just grab data from a hard-coded pointer address and decrement it (and, I suspect, return the decremented address).

Nothing too "scary", but definitely something a little dodgy about not using a damn ASSEMBLER, especially if it's just on its own, though.

Seriously - this will not work for the majority of compilers / OS because of memory protections like DEP, etc. If you want to run assembler in your C code, use an ASSEMBLER (e.g. nasm), then compile the code in that, then link that compiled code (.o file) into your C program and call it as a normal C function. That way, it *won't* be left in an area of memory marked non-executable and cause all sorts of errors, and you won't have to hard-code compiled machine code by a hex string (which is a ridiculous way to try to program).

I would say judging by this person's post history, they're up to no good. Some sort of remote spy application.

> I would say judging by this person's post history, they're up to no good.

Does anything look sketchy about any of these threads:
- http://cboard.cprogramming.com/linux...en-stdout.html (exec hacks)
- http://cboard.cprogramming.com/linux...assembler.html (shellcode?)
- http://cboard.cprogramming.com/netwo...-one-time.html (sending a virus maybe?)
- http://cboard.cprogramming.com/windo...r-command.html (obviously precursor to a malicious program)
- http://cboard.cprogramming.com/windo...escriptor.html (requesting information about windows security)
- http://cboard.cprogramming.com/linux...-question.html (packet forging)
- http://cboard.cprogramming.com/linux...packet-ip.html (raw socket trickery)
- http://cboard.cprogramming.com/linux...ort-my-pc.html (trying to portscan)

Yeah, we're not helping you.