Re: Crash in db_parse_context_get_m_header_internal

Hi Whitney,

On Tue, Apr 26, 2011 at 09:02:38AM -0500, [email protected] wrote:
> I've seen a few crashes on the 0.8.0 release coming from
> db_parse_context_get_m_header_internal. The stack trace looks like:
> 
> strncpy
> db_parse_context_get_m_header_internal
> parse_mhfd
> ipod_parse_artwork_db
> itdb_parse
> 
> Is it possible for the MHeader header_id to be pointing to invalid memory at this point?

Might be, or it might be the content of the header that is NULL. By any
chance, would you have a backtrace with debug symbols, a core, an ArtworkDB
triggering the bug, ... ?

Christophe

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2

_______________________________________________
Gtkpod-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkpod-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4WGMoACgkQJKRp+3pW944IywCeOYrlSkDSHJJfOPS8ci8utF1F
dGoAn1hQrFnI3YrmCBEpo901Uc+P5f1f
=zlgi
-----END PGP SIGNATURE-----