Le mercredi 09 décembre 2009 à 23:57 +0900, Norbert Preining a écrit :
On Wed, 09 Dec 2009, Josselin Mouette wrote:
Dear TeXlive maintainers, do you know whether the ABI for libkpathsea4
could have changed? Otherwise this might simply be a bug in the library.
Yes, there is libkpathsea5
Hilmar Preusse hill...@web.de wrote:
On 09.12.09 Norbert Preining (prein...@logic.at) wrote:
Hi,
Anyone having experience with that, I never had one in the whole TeX
cycle I am here (there was always libkpathsea.so.4 AFAIR).
AFAIR the last so-name change in kpathsea happened before teTeX
On Do, 10 Dez 2009, Josselin Mouette wrote:
Strangely, the crash happens after Denis installed the experimental
version, including libkpathsea5, yet it happens in libkpathsea4.
The experimental packages depend on libkpathsea5
The usual cause of such issues is that both versions are loaded at
Hi Josselin,
more strange things ...
On Do, 10 Dez 2009, Josselin Mouette wrote:
Strangely, the crash happens after Denis installed the experimental
version, including libkpathsea5, yet it happens in libkpathsea4.
That made me wonder ...
The usual cause of such issues is that both versions
On Do, 10 Dez 2009, Norbert Preining wrote:
AFAIS libkpathsea is even statically linked into evince, I found
no appearance of it in ldd of /usr/bin/evince, /usr/lib/libevview.so.1.0.0 or
/usr/lib/libevdocument.so.1.0.0.
Rubbish, it is there ..
Le jeudi 10 décembre 2009 à 10:19 +0100, Josselin Mouette a écrit :
Le mercredi 09 décembre 2009 à 23:57 +0900, Norbert Preining a écrit :
On Wed, 09 Dec 2009, Josselin Mouette wrote:
Dear TeXlive maintainers, do you know whether the ABI for libkpathsea4
could have changed? Otherwise
On Do, 10 Dez 2009, Denis Laxalde wrote:
Also, there is no problem on an other system with i686 arch (this might
explain why Frank did not experience the crash ?).
Can you install evince-dbg and get a backtrace? in principle best is that
you set your ulimit for core files to something big:
Le jeudi 10 décembre 2009 à 15:53 +0100, Norbert Preining a écrit :
On Do, 10 Dez 2009, Denis Laxalde wrote:
Also, there is no problem on an other system with i686 arch (this might
explain why Frank did not experience the crash ?).
Can you install evince-dbg and get a backtrace? in
Le mardi 08 décembre 2009 à 16:59 -0500, Denis Laxalde a écrit :
I just installed TeX-Live 2009 (package texlive from experimental which
should enter unstable soon, I guess). Now, Evince cannot open DVI files
anymore, it just crashes (see output attached).
Dear TeXlive maintainers, do you
On Wed, 09 Dec 2009, Josselin Mouette wrote:
Dear TeXlive maintainers, do you know whether the ABI for libkpathsea4
could have changed? Otherwise this might simply be a bug in the library.
Yes, there is libkpathsea5 now, that is probably the diff. libkpathsea
is now thread safe and some more
On 09.12.09 Norbert Preining (prein...@logic.at) wrote:
Hi,
Anyone having experience with that, I never had one in the whole TeX
cycle I am here (there was always libkpathsea.so.4 AFAIR).
AFAIR the last so-name change in kpathsea happened before teTeX 3.0.
The maintainer changed the API
Package: evince
Version: 2.28.1-1
Severity: important
I just installed TeX-Live 2009 (package texlive from experimental which
should enter unstable soon, I guess). Now, Evince cannot open DVI files
anymore, it just crashes (see output attached).
I'll be glad to provide any further information.
oops, the previous attachment begins with some garbage, please consider
this one instead.
Cheers,
--
Denis
$ evince test.dvi
*** glibc detected *** evince: free(): invalid pointer: 0x014e6fe1 ***
=== Backtrace: =
/lib/libc.so.6[0x7f9d74780d56]
13 matches
Mail list logo
