|To:||firstname.lastname@example.org (Siders, Keith)|
|Subject:||Re: hot patching|
|From:||Alan Cox <email@example.com>|
|Date:||Fri, 15 Feb 2002 14:55:22 +0000 (GMT)|
|Cc:||firstname.lastname@example.org ('Alan Cox'), email@example.com ('firstname.lastname@example.org')|
|In-reply-to:||<7DF7BFDC95ECD411B4010090278A44CA1B7579@ATVX> from "Siders, Keith" at Feb 15, 2002 08:17:30 AM|
> When I looked at the ptrace code it looked to me like it was intended for > inserting breakpoints for the most part. Are you saying that I can patch Mostly yes > into a process and have it vector off to executable code? At this point I've > identified at least three types of patches: a jump, a call, and simply > overwrite a few instructions (the easiest and common to all types). I'd love > to _not_ need a driver. Have a look at how gdb implements "call functionname"
|<Prev in Thread]||Current Thread||[Next in Thread>|