Program Crash Data, core.5169 file, how do I read it
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
gdb core.5169..."/core.5169": not in executable format: File format not recognized
gdb -c core.5169...Reading symbols from shared object read from target memory...(no debugging symbols found)...done.
Using host libthread_db library "/lib/tls/libthread_db.so.1".
Loaded system supplied DSO at 0xffffe000
Core was generated by `s2u --daemon=yes'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7f38efe in ?? ()
I'm not too sure if this is going in the right direction.
I'm no debugger guru but that output looks very informative to me. It looks like the process that created that core file was running as a daemon. It may have been running an image called s2u, or maybe that is the user account that was running the process. My first guess is that s2u is the name of the binary. The process terminated due to a segmentation fault.
Any more than that would require someone with some experience using the debugger. At least you know that it was a daemon process and terminated due to a segmentation fault. If you want to know more then I think it's time to start reading the GNU Debugger user guide.
Distribution: Used many over the years, main ones now "CentOS", Slackware and Arch
I have the same problem on my system running Mandriva 2007 Free Edition and I have reached the same stage as you in the investigation (!) Assuming it's the right program, I found some info about dbus on http://freedesktop.org/wiki/Software_2fdbus. The first few lines are shown below.
D-Bus is a message bus system, a simple way for applications to talk to one another.
D-Bus supplies both a system daemon (for events such as "new hardware device added" or "printer queue changed") and a per-user-login-session daemon (for general IPC needs among user applications). Also, the message bus is built on top of a general one-to-one message passing framework, which can be used by any two apps to communicate directly (without going through the message bus daemon). Currently the communicating applications are on one computer, but TCP/IP option is available and remote support planned.