xbmc/xbmc — comment on commit 8db08c3c794cbffe66b6107812e74d6726dea827
File:  line 0
By jmarshallnz:

Is there any way to get a usable stack trace from the crash by building libid3tag debug so that the users (who seem to be the only ones that can reproduce the issue) can get us some more useful info.

Reason is that we may hit the same problem in TagLib or whatever other library we're using in future.

The only thing I can see that we're doing differently is skipping over some early comment tags that have a short description set. There is some potential issues with the new code (eg it's possible that we use a 'corrupt' frame's encoding on the previous frames' short description) but nothing that that should lead to a crash - libid3tag gives us const pointers to ucs4 data - there's no allocation of new data in this routine or writing of data.