On 01/25, Denys Vlasenko wrote: > > On Tue, Jan 10, 2012 at 12:48 PM, Srikar Dronamraju > <srikar@xxxxxxxxxxxxxxxxxx> wrote: > > +/* > > + * opcodes we'll probably never support: > > + * 6c-6d, e4-e5, ec-ed - in > > + * 6e-6f, e6-e7, ee-ef - out > > + * cc, cd - int3, int > > I imagine desire to set a breakpoint on int 0x80 will be rather typical. > (Same for sysenter). May be uprobes will support this later. But imho we should not try to do this now. With the current code, afaics we do not want to allow the UTASK_SSTEP/TIF_SINGLESTEP task to enter the kernel mode, this state is "too special". Just for example, suppose it clones another task and the child gets the invalid uprobe state. Oleg. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>