examples\system\sysview_tracing_heap_log generate svdat can not analysis. (IDFGH-9080) #10483
Closed
3 tasks done
Labels
Resolution: NA
Issue resolution is unavailable
Status: Done
Issue is done internally
Type: Bug
bugs in IDF
Answers checklist.
IDF version.
v4.4.3-release
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
At project README.md introduce, when I use gdbinit command
esp sysview start file://heap_log.svdat
(I change the route to compatible my PC) generate svdat file and I should use the file open with systemview software.And as the doc introduce, when I use
$IDF_PATH/tools/esp_app_trace/sysviewtrace_proc.py -p -b build/sysview_tracing_heap_log.elf /tmp/heap_log.svdat
to check the svdat, the output is:What is the actual behavior?
When I generate svdat is:
heap_log1.zip
(Please unzip this)
And when I use systemview, It show cannot parse:
When I use python file to parse:
PS D:\mine\debug_temp\sysview_tracing_heap_log>
python C:/Espressif/frameworks/esp-idf-v4.4.3/tools/esp_app_trace/sysviewtrace_proc.py -p -b build/sysview_tracing_heap_log.elf heap_log.svdat
Traceback (most recent call last):
File "C:/Espressif/frameworks/esp-idf-v4.4.3/tools/esp_app_trace/sysviewtrace_proc.py", line 140, in
main()
File "C:/Espressif/frameworks/esp-idf-v4.4.3/tools/esp_app_trace/sysviewtrace_proc.py", line 90, in main
reader = apptrace.reader_create(trace_source, args.tmo)
File "C:\Espressif\frameworks\esp-idf-v4.4.3\tools\esp_app_trace\espytrace\apptrace.py", line 357, in reader_create
return FileReader(trc_src[7:], tmo)
File "C:\Espressif\frameworks\esp-idf-v4.4.3\tools\esp_app_trace\espytrace\apptrace.py", line 179, in init
self.trace_file = open(path, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: 'g3.svdat'
Steps to reproduce.
I am not use gdbinit file, I am take break at
heap_trace_stop()
:When the program stop at there, I am stop sysview in telnet.
Build or installation Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: