Bug 3157 - Custom Syscall observer results in no thread trace in EventViewer
Summary: Custom Syscall observer results in no thread trace in EventViewer
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 3399
  Show dependency treegraph
Reported: 2006-08-31 12:33 UTC by Mike Cvet
Modified: 2006-12-24 14:13 UTC (History)
3 users (show)

See Also:
Last reconfirmed:

Shot of the messed up trace (39.62 KB, image/png)
2006-08-31 12:35 UTC, Mike Cvet

Note You need to log in before you can comment on or make changes to this bug.
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!