[PATCH 0/4] Fixes to gdbstub.

[Srikar Dronamraju]

Hi Frank, 

Please review the set of patches for gdbstub. 
These are based on your maintained tree.
utrace-next/utrace-gdbstub-uprobes branch.
(1afe698c3228e67c43db6343b383a13e27e7f11a)


I have explicitly run checkpatch.pl to remove any formatting warnings /
errors.  However the formatting in these patches may be different from
other parts of the code.


At this time we have couple of known issues.

1. register_uprobe/unregister_uprobe may cause deadlock( I am looking at
this).

2. Even when we havent registered a breakpoint, there is a request for
breakpoint. (Not sure why gdbstub is asking for the breakpoint which is
never hit).

3. Sometimes entering data when the first breakpoint gets hit results in
SIGSTOP being sent to the traced process.

4. Uprobes may do postprocessing even when singlestep hasnt happened.
(I am looking at this too).

5. Supporting Multithreaded programs.

Also we might have to do cleaning up of code as per checkpatch.pl before
submission to LKML.

Subject: [PATCH 0/4] Fixes to gdbstub.
File: /tmp/gdbstub-patches/1/intro
Subject: [PATCH 1/4] Fix report signal callback to work more reliably.
File: /tmp/gdbstub-patches/1/gdbstub_signal_callback.patch
Subject: [PATCH 2/4] Fix possible double detach of engine
File: /tmp/gdbstub-patches/1/fix_double_detach.patch
Subject: [PATCH 3/4] Unregister uprobes after detach gdbstub engine
File: /tmp/gdbstub-patches/1/unreg_after_detach.patch
Subject: [PATCH 4/4] Stop once even for multiple interrupt requests
File: /tmp/gdbstub-patches/1/only_stop_once.patch

--
Thanks and Regards
Srikar Dronamraju