On Sat, Jan 13, 2007 at 06:45:36PM +0100, Andreas Henriksson wrote: > reassign 405801 libid3tag0 > tags 405801 + patch > thanks > > libid3tag doesn't gracefully handle unexpected values in the > files id3 encoding. Below is one such occation when id3_parse_uint > apparently returns 50 (which I have no idea how it can be stored in an > enum which doesn't contain a definition for 50). > The "id3_parse_string" function doesn't have a default case in it's > switch to catch this but (by accident?) happens to return NULL for this > case. No error checking seems to be done in this particular caller to > see if id3_parse_string returns NULL.
Hi, Thanks for look at this. Could you please also provide a sample case where it goes wrong, so I can really look at what's going on? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
