Jan Engelhardt wrote:
On Thursday 2013-08-22 02:14, Linda Walsh wrote:
that you have disabled (unless suse did it for all products, but that would seem unbelievably irresponsible, so I may be erring on the side of naivety)... but couldn't imagine a linux vendor doing something so irresponsible...
If you think so lowly of openSUSE, then you should just quit.
Those are YOUR thoughts and feelings. They are not based in what I said. To the contrary, I said I *couldn't imagine* openSuSE doing that. AFAIK, they didn't. My system settings say the default is to allow coredumps. I'm sorry, but now you are making stuff up and telling me that I should do something based on something you made up (which has nothing to do with what I said).
even MS sends coredump info back for analysis...
In light of the NSA revealings, not *sending* coredumps by default on Linux seems a godsend. Of course only to those concerned, the rest will ignore it.
In light of the NSA revealings, they already have access to virtually everything on your system, so *sending* coredumps or not, is rather irrelevant, not to mention it's probably less of an issue with Linux than with windows where they likely have automated tools that were created w/the help of MS. The fact that people fall all over themselves with the NSA approved SELINUX security, and that it is built into all of the programs and utilities whether you use it or not, worries me considerably more than concerns about them pouring through core dumps. Ever seen a SuSE build w/o the NSA-approved SELINUX hooks and libs required to be linked & loaded?
---- So, I not only "cover" your accusation of me accusing the with a counter accusation against you for wrongly dismissing the accusations, but raise the absurdity level of the Joerg, complaining about lack of symbols in his OWN stack backtrace program
Your funny quoting style aside, two (independent) things:
1. openSUSE has coredumps disabled by default - and you probably did not turn it on,
Interesting -- my /etc/sysconfig/ulimit has: ## Type: string ## Default: "unlimited" # # Limit the size of core dump files. 0 turns them off. # Hard limit: Can not be increased by non-root. # Corresponds to ulimit -Hc. # Parameter is in blocks (1k), 0 means turning core files off. # HARDCORELIMIT='unlimited' Did this change come recently? It seems 'filesystem-12.3' owns that file. Besides that point, I *do* get coredumps with other programs, when I don't it's because the application has disabled them.
2. debug symbols are in a separate package - whicih you probably did not install either - causing backtrace functions to not be able to print anything useful in the "default install" (much to the dismay of Jörg, but whatever).
When I get a coredump, and want to print a stack trace, I know to do that. This is a case where the normal function of the program is impeded or broken because it assumes those symbols will be there. So the reason there are no symbols in Joerg's default output is because openSuSE didn't ensure the programs dependencies were installed along with the program. Maybe Joerg's next OSuse release will have an explicit dependency for the debug symbols in his rpm or in the binary... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org