Cmus segmentation fault how to#

If you don't have an error message before segmentation fault.

apport-bug logs / core dump / backtrace.

I mean there are many other useful tools out there that you gonna find when you dig in more. That's means that you are breaking the user abstraction level and opening the black box! (FLOSS actually has transparent box). At least, you may be able to collect enough debug data that help resolve the issue when reporting it. There many bug reports out there inactive for years. If you you have even a little programming background, it is recommended that you try your best to resolve it yourself.

Cmus segmentation fault how to#

For 3rd party closed source, check their help pages how to report bugs and collect related data. If open source supported by Ubuntu use ubuntu-bug ( apport-bug). fire a bug report, see How do I report a bug? If you didn't make any custom configuration/setup and you all updates installed. And most of the cases end up with a bug report, either for target program or one of its dependencies (either upstream project or downstream distribution package). However, it is not always easy find the cause with large programs or those which relay on other project lib's. Some cases: Reading value with uninitialized pointer, Going out of range in an array, Function call (when backward compatibility not maintained). The program tried to access a memory area out side its own section. The simplest description I can come with (may be not the perfect): See AU: What is a segmentation fault? post and also this post which have some examples how reproduce it, SO: What is segmentation fault?.