Not quite certain how to do this but copied what I think you asked for below - Richard
richard@richard-Aspire-5610:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log <program> <arguments> bash: syntax error near unexpected token `<' richard@richard-Aspire-5610:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log <program> <arguments><evolution> bash: syntax error near unexpected token `<' richard@richard-Aspire-5610:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log <program> <arguments> bash: syntax error near unexpected token `<' richard@richard-Aspire-5610:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log <program> <arguments>which <evolution> bash: syntax error near unexpected token `<' richard@richard-Aspire-5610:~$ evolution EI: MAIL PREFSSegmentation fault richard@richard-Aspire-5610:~$ tar -zcf valgrind-logs-<program>.tar.gz valgrind.log* bash: program: No such file or directory richard@richard-Aspire-5610:~$ On Thu, 2011-01-20 at 17:31 +0000, Omer Akram wrote: > if the issue is reproduce able could you please get Valgrind logs by > following the method here https://wiki.ubuntu.com/Valgrind this one is > quite a critical crasher that people have been reporting over the last > couple of days > > ** Visibility changed to: Public > > ** Changed in: evolution (Ubuntu) > Importance: Medium => High > > ** Changed in: evolution (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. https://bugs.launchpad.net/bugs/705310 Title: evolution crashed with SIGSEGV in memalign() -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
