Thank you for opening this bug and helping make Ubuntu better. You might
want to know that, as a general rule, bugs with coredumps should not be
made public for privacy reasons. The automatic coredump analyser will
work on the bug, and provide nice stacktraces for us to marvel on -- and
then remove the coredump. When that happens, we will look at the bug and
-- if no other visible private data is found -- mark it public.
As such, I am moving your bug back as Private, just in case.
Meranwhile, I have a question: can you repeat this error at will? this
is a segv very early in the start of the programme... if so, can you
givce us the exact command?
** Visibility changed to: Private
** Changed in: coreutils (Ubuntu)
Importance: Undecided => Medium
** Changed in: coreutils (Ubuntu)
Status: New => Incomplete
--
mv crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/535394
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
