On Tue, Apr 26, 2011 at 09:02:38AM -0500, wbyoung@... 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:
> 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, ... ?