From: Quinn Dunkan <quinn@barf.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhog the corruptor!
Date: Tue, 13 Nov 2001 15:28:37 -0800 [thread overview]
Message-ID: <20011113232842.C7CAC9C404@barf.ugcs.caltech.edu> (raw)
In-Reply-To: Your message of "Tue, 13 Nov 2001 18:04:46 EST." <20011113230455.25131199B9@mail.cse.psu.edu>
> Brucee's implementation just patches the call to point to the
> correct destination. You don't have to walk any machine code.
> The (modified) linker emits a known call instruction, and relocation
> information which says where it is and what symbol to patch
> it with. Symbol lookup is done in a highly controlled way.
This is just for kernel drivers, right? While plan9's non-support of dynamic
linking for arbitrary C programs works just fine, it doesn't seem to work so
well for languages that only load libraries at run time, such as python or
perl (or limbo?). If the linker can write relocation information, would that
make it easier to write a dlopen()-like function?
next prev parent reply other threads:[~2001-11-13 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 23:04 David Gordon Hogan
2001-11-13 23:28 ` Quinn Dunkan [this message]
2001-11-13 23:38 ` Chris Hollis-Locke
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 9:26 forsyth
2001-11-16 11:56 ` Boyd Roberts
2001-11-13 23:54 forsyth
2001-11-13 23:53 David Gordon Hogan
2001-11-13 23:50 David Gordon Hogan
2001-11-14 0:34 ` Quinn Dunkan
2001-11-14 4:46 ` Lucio De Re
2001-11-16 11:52 ` Boyd Roberts
2001-11-13 22:53 anothy
2001-11-13 22:59 ` George Michaelson
2001-11-13 22:32 David Gordon Hogan
2001-11-13 22:09 anothy
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=20011113232842.C7CAC9C404@barf.ugcs.caltech.edu \
--to=quinn@barf.ugcs.caltech.edu \
--cc=9fans@cse.psu.edu \
/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).