'show active trace', or 'acttrace' for short, prints backtraces from running
threads only.
Details
Details
- Reviewers
jhb mjg - Commits
- rS304828: ddb: Add 'show active trace' command
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 4936 Build 4999: arc lint + arc unit
Event Timeline
sys/ddb/db_command.c | ||
---|---|---|
837 | I think it would be beneficial (apart from introduction the acctrace command) to extend the default output with cpu number, if given thread is running. Other than that looks good to me, thanks. |
sys/ddb/db_command.c | ||
---|---|---|
837 | The active_only (acttrace) output does include td_oncpu. It's the other clause of the if :-). Or do you mean, I should add oncpu output to "all trace" as well? |
sys/ddb/db_command.c | ||
---|---|---|
837 | The latter. |
sys/ddb/db_command.c | ||
---|---|---|
837 | To be more specific, either only print CPU if the thread is running OR print CPU unconditionally along with the state, so that one can tell if it is on cpu (as opposed to having a note what last cpu it was on). |