On SteamOS, gpuvis failed to visualize the captured trace file.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 910
- Forks
- 104
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
On SteamOS,
-
Use the sample scripts at folder ./gpuvis/sample to capture a event trace.
$ sudo ./trace-cmd-setup.sh
$ sudo ./trace-cmd-start-tracing.sh
$ sudo ./trace-cmd-capture.sh
$ sudo ./trace-cmd-stop-tracing.sh
Then a file named trace_02-02-2023_13-20-27.dat is created -
Use gpuvis application to visualize.
$ gpuvis trace_02-02-2023_13-20-27.dat
It failed with errors shown as below.
[Error] read_header_files: header_page not found.
[Error] read_trace_file: setjmp error called for trace_02-02-2023_13-20-27.dat
[Error] load_trace_file(trace_02-02-2023_13-20-27.dat) failed.
Is there anybody experienced this error?
It is deeply appreciated for any suggestions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the scripts in ./gpuvis/sample: trace-cmd-setup.sh, trace-cmd-start-tracing.sh, trace-cmd-capture.sh, and trace-cmd-stop-tracing.sh, then open the generated .dat file with gpuvis on SteamOS. Use the read_header_files and read_trace_file errors as the starting point; done means the captured trace loads or the incompatibility is clearly diagnosed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100