Bug 3157

Summary:	Custom Syscall observer results in no thread trace in EventViewer
Product:	frysk	Reporter:	Mike Cvet <mcvet>
Component:	general	Assignee:	Unassigned <frysk-bugzilla>
Status:	ASSIGNED ---
Severity:	normal	CC:	mark, npremji, pmuldoon
Priority:	P2
Version:	unspecified
Target Milestone:	---
Host:		Target:
Build:		Last reconfirmed:
Bug Depends on:
Bug Blocks:	3399
Attachments:	Shot of the messed up trace

Description Mike Cvet 2006-08-31 12:33:48 UTC

If you create a new custom observer based on a syscall observer, add it to the
session, and re-start the session, one or more of the processes in the process
group will not have a thread trace - just the proc name. See the screenshot...

Comment 1 Mike Cvet 2006-08-31 12:35:04 UTC

Created attachment 1268 [details]
Shot of the messed up trace

Should be two lines - one for the process, and one for the thread.

Notice how the threads box is also empty.

Comment 2 Mike Cvet 2006-08-31 12:39:01 UTC

Might be more of a problem than I thought - when I exited Frysk this time, all
the zsh processes from that screenshot were killed!