On Mon, Jul 25, 2011 at 09:39:53PM +0200, Stefan Seyfried wrote:
Am Mon, 25 Jul 2011 15:20:42 -0400 schrieb Cristian Rodríguez <crrodriguez@opensuse.org>:
El 25/07/11 04:29, Stefan Seyfried escribió:
Cool, thanks. I'm now running it under valgrind instead of gdb, this will hopefully tell us where the memory is freed.
Having glibc "screaming in pain" :-) is pretty nice.. I have looked the source code of the package but cannot find *where the %$%" battery is getting freed.
Maybe it is some libnotify magic or something like that.
I'm actually suspecting a change in a third party library since xfce4-power-manager code did not change for months and only recently started crashing (I'm always on FACTORY, so always with MALLOC_PERTURB and friends)
We'll see what valgrind has to say about the issue. I screwed up the first attempt because I did not redirect output in a file and have only 5000 lines of scrollback in my terminal - which was not enough :-)
Actually 0xaaaaaaaaaaaaaa is probably not MALLOC_PERTURB_, but just uninitialized or overwritten memory. Check if it ever gets initialized? But valgrind should spot that too. Ciao, MArfcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org