Re: ERROR: *** glibc detected *** double free or corruption
Frederic Gobry <[email protected]> Fri, 10 Mar 2006 14:23:24 +0100
| Newsgroups | gmane.comp.gnome.apps.pybliographer |
|---|---|
| Message-ID | <[email protected]> |
> Playing with valgrid I (once) got a traceback:
>
> $ MALLOC_CHECK_="1" valgrind -v pybliographic
> [...]
> This is Pybliographic 1.2.8 [Python 2.4.2, Gtk 2.8.8, PyGTK 2.8.2]
> *** glibc detected *** free(): invalid pointer: 0x084ee710 ***
> *** glibc detected *** free(): invalid pointer: 0x084f40b0 ***
> *** glibc detected *** free(): invalid pointer: 0x084f7af8 ***
> Traceback (most recent call last):
> File "/usr/share/pybliographer/Pyblio/GnomeUI/Document.py", line 746, in save_document_as
> out = file, how = how, database=self.data)
> File "/usr/share/pybliographer/Pyblio/Open.py", line 199, in bibwrite
> writer (iter, out, preamble=preamble)
> File "/usr/share/pybliographer/Pyblio/Format/BibTeX.py", line 673, in writer
> entry_write (entry, output)
> File "/usr/share/pybliographer/Pyblio/Format/BibTeX.py", line 547, in entry_write
> for field in entry.keys ():
> IOError: can't parse entry `@preamble{{S{HARP}s: mammalian enhancer-of-split- and hairy-related proteins coupled to neuronal stimulation.@{{O}}'
Interesting!
> Where do the curly parentheses in "{S{HARP}s:" come from ..?
BibTeX tends to normalize case in some fields, like titles, so in order
to provide pseudo-WYSIWYG behavior, generated BibTeX adds braces to
preserve case when needed. I need to see why the IOError occurs, though.
Frédéric
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEEX3MFjQHpltE9KURAikJAJ42wBavrSuEGhtSzq1yHTgvajaauwCeLgGn /l3TW0Zlnqt052K8UHQvh7o= =k6Px -----END PGP SIGNATURE-----