[Bug 452399] Re: gconftool-2 crashed with SIGSEGV in g_slice_alloc()

[IDWMaster]

Unfortunately; I was unable to reproduce the problem using valgrind.
This is also an intermittent problem and gconftool-2 is not the only
program that crashes after resuming (see the other most recent bug
reports that I posted).  More details below:

I downloaded and installed the large program (Valgrind) but was unable
to reproduce the error, because gconftool-2 was started by the system
and I was not sure how it had been started; or what parameters were used
to start the task at the time. This is also an intermittent problem.
When I tried running gconftool-2 without any parameters; I received the
message "Run 'gconftool-2 --help' to see a full list of available
command line options."


Is there a way to trace down the parameters that were passed to gconftool-2 at the time the issue occurs? Should I test my computer for defective RAM?

-- 
gconftool-2 crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/452399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs