From: Blake McBride <blake@arahant.com>
To: linux-assembly@vger.kernel.org
Subject: Need help doing a jmp rather than a call
Date: Fri, 8 Nov 2013 21:02:54 -0600 [thread overview]
Message-ID: <l5k8kk$9kd$1@ger.gmane.org> (raw)
I am trying to get a simple piece of x64 assembly working on 64 bit
linux and a Mac. I am using GCC.
Let's say I have 4 (C language) functions. Function fun1 calls fun2,
fun2 calls fun3, and fun3 calls fun4. I need fun 4 to operate and run
as if it was called directly from fun1. So, fun4 should see the
arguments passed to fun2, and when fun4 returns it should return
diretly to fun1 as if it was called by fun1.
Basically, this is an OO language that uses fun2 to calculate what fun4
is. fun3 is used to manipulate the stack so that when fun4 starts up
it thinks it was called directly from fun1. fin1, fun2, and fun4 are
plain C code. fun3 performs the magic. I have been doing this easily
on many different 32 bit machines for years but I haven't been able to
get it going on 64 bit machines.
Typically fun3 would:
1. create a new stack frame
2. call fun3
3. pop local call frame
4. return
What I need fun3 to do is:
1. either pop its stack frame or don't create one
2. pop the stack frame from fun2
3. jump to fun4
Then fun4 will start executing as if it was called from fun1. I have
sample (errant) C code for the entire process. It will all work fine
if fun3 (_jumpToMethod) is rewritten in assembler.
(What I did in the past was compile the C code for _jumpToMethod into
assembly code, modify the code, and then use that assembly code.)
Here is the C code for fun1, fun2, and fun3:
#include <stdio.h>
char *obj = "Some object pointer";
char *GenObj = "Some Generic Object Pointer";
typedef int (*ofun)();
int Method(char *self, int a, int b, int c) /* fun4 */
{
printf("Method reached with args %s %d %d %d\n", self, a, b, c);
return a + b + c;
}
ofun FindMethod(char *obj, char *gen)
{
return Method;
}
GenericFunction(char *self, ...) /* fun2 */
{
_jumpToMethod( FindMethod(self, GenObj) );
}
main(void) /* fun1 */
{
printf("Method is at %lx\n", (long unsigned int) &Method);
/* both calls to Method should look alike to Method */
int r = Method(obj, 1, 2, 3);
printf("Value returned from GenericFunction = %d\n", r);
r = GenericFunction(obj, 1, 2, 3);
printf("Value returned from GenericFunction = %d\n", r);
return 0;
}
-----------------------------------------------------------------
Here is the C code for _jumpToMethod (fun3)
void _jumpToMethod(void (*function) (/* ??? */))
{
/* pop_this_stack_frame; */
/* pop previous (generics) stack frame */
(*function)(); /* must be changed to jump instruction */
}
I think this would be easy for someone who knows this assembly
language. I have spent about 5 hurs on it and I am lost as I can be.
Your help is greatly appreciated!
Thanks!
Blake McBride
next reply other threads:[~2013-11-09 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 3:02 Blake McBride [this message]
2013-11-09 6:19 ` Need help doing a jmp rather than a call Sofiane Akermoun
2013-11-09 8:21 ` Blake McBride
2013-11-09 10:57 ` Sofiane Akermoun
2013-11-09 11:00 ` Sofiane Akermoun
2013-11-09 14:13 ` Blake McBride
2013-11-09 14:42 ` Rob
2013-11-09 16:19 ` Blake McBride
2013-11-09 21:30 ` Rob
2013-11-09 22:47 ` Blake McBride
2013-11-10 0:01 ` Blake McBride
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='l5k8kk$9kd$1@ger.gmane.org' \
--to=blake@arahant.com \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).