IMHO, coredumps are for developers only, not even suitable for ops,
asking users for a coredump is really too much. If you want to deep
analyze a coredump, not only the coredump itself but also the system
shared libraries are also needed, most users have don't have the
skills to do this.
If you on
It's a start but I was really hoping for something that covers the
common pitfalls, too, and includes more of a walkthrough for the
uninitiated. I think I'll have to write it.
On Sat, Feb 14, 2015 at 12:05:00AM -0800, Andy Zhou wrote:
> A quick web search did not lead to anything directly usable.
A quick web search did not lead to anything directly usable. How about
the following.
---
Core files are usually generated in the same directory as the running
program with a name 'core'. However, whether a core file will be
generated, its filename and lo
Occasionally (as today) I find myself asking a user to get a core dump
and a backtrace, and find that the user doesn't have any of the skills
or knowledge to do that. Does anyone know of a good document that
walks a user through how to do this (not necessarily OVS-specific)? I
don't want to hand-
