«

I like it how even binary-based distros make debugger symbols available for
their binaries (I think these are in separate files that can be loaded by
the debugger, not in the main executables/libraries). It makes it so much
easier to isolate problems if/when they occur.

Look at this bug report
<https://bugzilla.redhat.com/show_bug.cgi?id=595830>, for example. I was
able to quickly narrow it down to a particular line of code, and figure out
that it could only happen if an array field had never had any items put into
it. A trivial way to reproduce this was to feed in a zero-length input movie
file.

Based on that, I can modify the code to add a check, output an error message
and abort at that point, instead of crashing.

As to why the user’s actual movie file was triggering the problem, we don’t
know yet. We’ll see if they’re willing to provide a sample we can use to
investigate the situation further.