Bugzilla

I can install symbolic without a problem. I was able to throw together a proof-of-concept script that opens a SYM file, parses it, and returns a `LineInfo` thing.

I then spent some quality time looking at the Tecken code. The SYM file parsing is entangled with symbol file downloading and also the symbolication view. I'm now extracting that code into a separate module with well-defined boundaries and tests. That makes it easier to build a second SYM file parser using symbolic, write some scaffolding to parse a file with both and compare the results, and then iterate on that.

So far, the project still seems doable. I haven't hit any hard blockers, yet.

Some questions that still need answering:

1. Is the SYM file parsing code too entangled to be extracted without breaking other things?
2. Does symbolic parse the SYM file and return the information the symbolicate view needs?
3. Is the symbolic parsing code slower or less performant in a meaningful way?

I can install symbolic without a problem. I was able to throw together a proof-of-concept script that opens a SYM file, parses it, and returns a `LineInfo` thing.

I then spent some quality time looking at the Tecken code. The SYM file parsing is entangled with symbol file downloading, caching of parsed output, and also the symbolication view. I'm now extracting the SYM file parsing code into a separate module with well-defined boundaries and tests. That makes it easier to build a second SYM file parser using symbolic, write some scaffolding to parse a file with both and compare the results, and then iterate on that.

So far, the project still seems doable. I haven't hit any hard blockers, yet.

Some questions that still need answering:

1. Is the SYM file parsing code too entangled to be extracted without breaking other things?
2. Does symbolic parse the SYM file and return the information the symbolicate view needs?
3. Is the symbolic parsing code slower or less performant in a meaningful way?