From: Josh Fryman <fryman@cc.gatech.edu>
To: linux-kernel@vger.kernel.org
Subject: silly memory question ...
Date: Mon, 27 Aug 2001 14:24:02 -0400 [thread overview]
Message-ID: <3B8A9042.4027049@cc.gatech.edu> (raw)
hi all,
i'm looking to do something stupid. can anyone tell me why it won't
work? (is there some kind of special protection on EXE memory pages?)
i have an application, App1, that has a 64KB function (64KB of NOP)
"void funcX(void)". App1 opens a socket to another application, App2,
which is going to feed code to App1 to stick in funcX.
that is, i've got some other set of functions i plan on feeding to App1
and they're all going to look like "funcX" to App1. those functions are
coming from App2, which is chewing on a bunch of var-things to spit out
just the right code for App1.
now, when i try to do this, i get Random Stuff. sometimes, i just get
a segfault. sometimes, it seems to work, but the memory at funcX is
hosed if i do a hex-dump compared to what i received from App2. either
way, it isn't doing what i want...
is there some trick here to make this work? or am i SOL?
[is there a better place to ask this question?]
thanks,
josh
next reply other threads:[~2001-08-27 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 18:24 Josh Fryman [this message]
[not found] <Pine.LNX.3.95.1010828101642.13417A-100000@chaos.analogic.com>
2001-08-28 14:47 ` silly memory question Josh Fryman
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=3B8A9042.4027049@cc.gatech.edu \
--to=fryman@cc.gatech.edu \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.