From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 8l -e
Date: Tue, 27 May 2014 17:33:48 -0400 [thread overview]
Message-ID: <c53218ff21c0f761325bb94a4f9c437b@ladd.quanstro.net> (raw)
In-Reply-To: <20140527213018.GQ3763@iota.offblast.org>
> ok. i'm beginning to understand better. is there a specific use case,
> such as the kernel or userland?
>
> i didn't see anything like a tool that could poke nops into the right
> places. i started to write an acid function to put the nops in one
> named function, and then i realized that the ret can appear several
> times in one function and i would need to search for and patch them
> out. but only the *first* ret, not second, e.g.:
this tool was ment for use with the kernel. there is a devtrace in 9atom's
pc and pcpae kernels that does this.
ron wrote a paper for the first athens, ga iwp9. i don't remember the year.
2009?
- erik
next prev parent reply other threads:[~2014-05-27 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 20:10 Nick Owens
2014-05-27 20:16 ` erik quanstrom
2014-05-27 21:30 ` Nick Owens
2014-05-27 21:33 ` erik quanstrom [this message]
2015-07-08 2:43 ` michaelian ennis
2015-07-08 2:44 ` michaelian ennis
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=c53218ff21c0f761325bb94a4f9c437b@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).