On Mon, 2009-08-10 at 12:42 -0400, Frank Ch. Eigler wrote:
Hi -
On Mon, Aug 03, 2009 at 11:10:00AM -0700, Jim Keniston wrote:
[...]
So as per my analysis, gdb_utrace_report_signal was called, followed by
uprobe_report_signal. Since gdb_utrace_report_signal requested for
UTRACE_STOP
* Jim Keniston jkeni...@us.ibm.com [2009-08-03 11:10:00]:
So as per my analysis, gdb_utrace_report_signal was called, followed by
uprobe_report_signal. Since gdb_utrace_report_signal requested for
UTRACE_STOP as resume action for SIGTRAP, the thread got stopped.
uprobes was waiting
The target process side is also hung:
zsh D 0002 3568 1288 1259 0x0080
880078c57b98 0046 00011d4a
88006d4b8000 880078c57f50 7fff138b0858
88006d4b83b8 f968
Hi, guys -
I'm running into a recurrent problem on my gdbstub+uprobes prototype.
(git://web.elastic.org/~fche/utrace-ext.git utrace-gdbstub-uprobes)
The gist is that running a unregister_uprobe upon a stopped process
(single-threaded, stoped via a UTRACE_STOP event) appears to hang
indefinitely.
