[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-08-20 Thread Timmy Shih Jun Yee
Evince no longer crashes when opening manual.dvi, so I'm closing this bug. However, the file cannot be opened (which itself is a separate bug; please file a new bug report for that). (I tested this with Evince 2.30.3-0ubuntu1.1 on Lucid.) ** Attachment added: "Screenshot of Evince not crashing wh

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-23 Thread Sebastien Bacher
** Changed in: evince (Ubuntu) Status: Incomplete => New -- evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 *** https://bugs.launchpad.net/bugs/513261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is sub

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-23 Thread fiat1100d
This is my Valgrind log, after a correct display ** Attachment added: "valgrind-logs-evince.tar.gz" http://launchpadlibrarian.net/39609439/valgrind-logs-evince.tar.gz -- evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 *** https://bugs.launchpad.net/b

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-23 Thread fiat1100d
I noticed the same behaviour reported by Lucian: - evince crashes when opening DVI without Valgrind; - it displays fine when slowly opening DVI using Valgrind; - after that the same DVI document still opens correctly when running without Valgrind. >From the debugger logs, I see that the ~/.texmf-

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-22 Thread Lucian Adrian Grijincu
These are the logs from running evince through valgrind the first time. ** Attachment added: "valgrind-logs-evince.tar.gz" http://launchpadlibrarian.net/39563219/valgrind-logs-evince.tar.gz -- evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 *** https

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-22 Thread Lucian Adrian Grijincu
There's some kind of heisenbug here. I ran evince on http://paultaylor.eu/diagrams/manual.dvi (downloaded it beforehand) and it crashed. I then ran G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log evince manua

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-22 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem. ** Changed in: evin

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-20 Thread Lucian Adrian Grijincu
For me, the problem appeared when trying to open http://paultaylor.eu/diagrams/manual.dvi Evince crashed before it would show the application window. -- evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 *** https://bugs.launchpad.net/bugs/513261 You recei

[Bug 513261] Re: evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 ***

2010-02-20 Thread fiat1100d
** Visibility changed to: Public -- evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 *** https://bugs.launchpad.net/bugs/513261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -