getting track info causes a segv on some files
Status: Beta
Brought to you by:
dzongker
I had some problems using pyid3lib where certain files
would cause the python interpreter to trigger a
segmentation violation. I tracked it down to an id3lib
function giving back a null pointer, which raises the
segv in strchr soon after. The attached patch remedies
this problem.