Hi Frank, Utrace-devel The first two patches in this patchset fix report_signal callbacks in uprobes and gdbstub.
>From Rolands message to utrace-devel, https://www.redhat.com/archives/utrace-devel/2009-August/msg00146.html we could rely on orig_ka == NULL to know if info->si_signo field for signal number indicates an actual signal or stale data. Roland, Oleg, can you please comment on the above check. This patchset changes report_signal callback of gdbstub engine so that it works similarly irrespective of the order in which they are connected. When two engines interested in the same event on a same task are attached, the order of report callbacks for that event depends on engine attach order. This is very important for gdbstub because uprobes report_signal can change the instruction pointer. The other patch fixes a bug introduced in recent defer registration patch. Subject: [PATCH 0/3] Fixes to gdbstub, uprobes. File: /tmp/gdbstub-patches/3/intro Subject: [PATCH 1/3] rework report_signal callback. File: /tmp/gdbstub-patches/3/redo_gdbstub_report_signal.patch Subject: [PATCH 2/3] Make singlestep in uprobes more robust. File: /tmp/gdbstub-patches/3/verify_and_then_post_process.patch Subject: [PATCH 3/3] Fix a bug in defer registration patch. File: /tmp/gdbstub-patches/3/fix_bug_defer_reg.patch -- Thanks and Regards Srikar Dronamraju
