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

> On Thu, 9 Mar 2006, Ingo Bormuth wrote:
> 
> >   This is Pybliographic 1.2.8 [Python 2.4.2, Gtk 2.8.8, PyGTK 2.8.2]
> >   *** glibc detected *** double free or corruption (!prev):
> > 0x084d43b8 ***

This is driving me crazy too. I don't have a solution, but after
a lot of systematic experimentation I traced the problem to the
length of the Title in the offending references. Here's how I came to
that conclusion.

Get any one of these PMID references through Medline Query:

PMID- 11423663
PMID- 12110674
PMID- 11283252

If you try to save any of these as a BibTeX file, pybliographic will
hang print the error exactly as reported by Ingo. Kill it.

So...start over. Get the reference again through Medline Query.
Now, within pybliographic, select the reference and choose edit.
In the edit window, make the title either 1 character longer or 1
character shorter. Apply the edits. Save as a BibTeX file. It should
not hang this time. It's Magic, thank you very much.

Now, select the reference again and choose edit. In the edit window,
restore the title to its original length. Now when you try to apply the
edit, pybliographic will hang again with the glibc error.

This worked for me for all three example references. Oh, and it worked
for Ingo's PMID example (9361282) too.

I apologize for not being able to push this to the problem code. But I
hope it helps with the bug tracking.

Cheers,
Mitch
-- 
M. Mitchell Smith			[email protected]
Department of Microbiology		Phone: (434) 924-2669
University of Virginia			FAX:   (434) 982-1071
Charlottesville, VA 22908


-------------------------------------------------------
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