Messages in this thread |  | | | Date | Fri, 25 Sep 2009 12:14:49 +0200 | | From | Arjan van de Ven <> | | Subject | Re: Immediate values |
| |
On Fri, 25 Sep 2009 11:02:06 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > Then, following your advice, kprobes should be re-designed to do a > > stop_machine around the int3 breakpoint insertion ? And gdb > > should be stopping all threads of a target process before inserting > > a breakpoint. Therefore, I do not seem to be the only one confused > > about Intel statement on this issue. > > There was considerable discussion abut this when the kprobe stuff went > in. If I remember rightly it was stated by someone @intel.com then > that int3 was ok (even though its not strictly documented as such). > The same is not true for all instructions on all x86 processors > unfortunately.
specifically, using int3 *and then going back to the old value*.
-- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org
|  |