Steve> I'm more interested in the perf/trace than gdb, as the way gdb is mostly Steve> used (at least now) to debug problems in the code with a big hammer Steve> (single step, look at registers/variables). That is, gdb is usually very Steve> interactive and its best to "stop the code" from running to examine what Steve> has happened. gdb is not something you will run on an application that Steve> is being used by others. It depends. People do in fact do this stuff. In recent years gdb got its own implementation of "always inserted" breakpoints (basically the same idea as uprobes) to support some trickier multi-thread debugging scenarios. Tom -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx 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>