Add timing to debug-sym-file.py

[willkg]

Along with debugging sym file structure, this gives us some information about how long it took symbolic to parse it.

Generally, I only use this script for debugging dump_syms and symbolic problems. Adding timing to it and changing it to use eliot.libsymbolic parse function gives it some additional future utility around speeding up symbols file parsing.

To use, download a symbols file and then:

$ make shell
app@0b29887b3279:/app$ ./bin/debug-sym-file.py libxul.so.sym 
libxul.so.sym
size: 699,495,515
first line: ['MODULE', 'Linux', 'x86', '015C5165CC511800A25E59423F0D5CB40', 'libxul.so']
parsing sym file with symbolic ... 10.472s
app@0b29887b3279:/app$ 

[smarnach]

Looks good to me. Also looks like either my system is slower than yours, or Windows symbols files are slower to parse:

$ bin/debug-sym-file.py xul.pdb/26D7EB25B4D3AB484C4C44205044422E1/xul.sym 
xul.pdb/26D7EB25B4D3AB484C4C44205044422E1/xul.sym
size: 643,048,158
first line: ['MODULE', 'windows', 'x86_64', '26D7EB25B4D3AB484C4C44205044422E1', 'xul.pdb']
parsing sym file with symbolic ... 22.208s

[willkg]

app@70abba933371:/app$ ./bin/debug-sym-file.py xul.sym 
xul.sym
size: 643,048,158
first line: ['MODULE', 'windows', 'x86_64', '26D7EB25B4D3AB484C4C44205044422E1', 'xul.pdb']
parsing sym file with symbolic ... 13.553s
app@70abba933371:/app$ 

I did my last laptop refresh a little under a year ago, I think. When was your last one?

[willkg]

Thank you!