Re: ERROR: *** glibc detected *** double free or corruption

>> *** glibc detected *** double free or corruption (!prev): 0x084d43b8 
>> An example for a reference triggering the mentioned error is PMID: 9361282

> Hm. Perfoming a medline query for 'PMID: 9361282', and after saving the 
> entry as bibtex works for me without errors.

Here the described bug is absolutely reproducable.

Reading man malloc I played with setting MALLOC_CHECK_:

MALLOC_CHECK_="0"   -->  Pybliographer silently hangs 
                         No error message
                         Bibtex file is empty or truncated at random position 

MALLOC_CHECK_="1"   -->  Bibtex file gets written
                         Pybliographer does NOT hang or die
                         Bibtex file is written properly

MALLOC_CHECK_="2"   -->  Dialog box asks me weather to quit or restart.
                         No error in terminal
                         Bibtex file is truncated (last line: "@Article{RDG+97,")

So my workaround is to use MALLOC_CHECK_="1" but I think there is a bug hidden 
somewhere.

I'm a bit irritated, that MALLOC_CHECK_="2" gives me a meaningless error
dialog but no debug output. Is there a way to make pybliographer (or
python) more verbose?

-- 
Ingo Bormuth, voicebox & telefax: +49-12125-10226517       '(~o-o~)'
public key 86326EC9, http://ibormuth.efil.de/contact   --ooO--(.)--Ooo--



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642