We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Hello
Is this problem present with the latest updated Karmic's, Lucid's or Maverick's
packages?
Thanks in advance
Fabio
** Changed in: ubuntu
Status: New = Incomplete
--
armel/versatile: glibc detected double-free or corruption (!prev)
https://bugs.launchpad.net/bugs/520465
You received
if there's evidence that this problem is tracked down to eglibc, then
please comment, don't just reassign.
** Package changed: eglibc (Ubuntu) = ubuntu
--
armel/versatile: glibc detected double-free or corruption (!prev)
https://bugs.launchpad.net/bugs/520465
You received this bug notification
** Package changed: ubuntu = eglibc (Ubuntu)
--
armel/versatile: glibc detected double-free or corruption (!prev)
https://bugs.launchpad.net/bugs/520465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Workaround:
set G_SLICE=always-malloc for glib/gtk+ programs, or set MALLOC_CHECK_=0; the
latter is a bit of a heavy workaround though and this might hide real issues.
I didn't manage to use G_SLICE=debug-blocks to debug this.
--
armel/versatile: glibc detected double-free or corruption
Sorry, forgot one line of output when running slice-test after the help output:
Starting 1 threads allocating random blocks = 1021 bytes with seed=random
using slab allocator + magazine cache
--
armel/versatile: glibc detected double-free or corruption (!prev)
