Image does not create a core files for debugging

Asked by Rusty Lynch on 2009-08-28

When a process segfaults, the OS is not creating a core file which is needed for debugging.

Question information

Language:
English Edit question
Status:
Answered
For:
sudbury Edit question
Assignee:
No assignee Edit question
Last query:
2009-08-28
Last reply:
2009-09-01
Henry Hall (hlh) said : #1

An answer will be forthcoming

Bill Filler (bfiller) said : #2

One option is to use apport. apport is installed by default in the images, but it not enabled. To enable, do the following:
sudo vi /etc/default/apport and set enabled=1
then restart apport by sudo /etc/init.d/apport restart.

When a program crashes it will create a .crash file in /var/crash. This file contains the core file and other useful information. In Ubunutu there is a panel applet that will notify the user a crash occurred and prompt them to send it. In our case this notification doesn't occur, but the tester can manually upload the .crash file in the bug report.

There are other packages to analyze the .crash files like apport-unpack and apport-retrace that the developers can use to look at the crash.

See https://wiki.ubuntu.com/Apport for much better details, but this is quite simple.

Bill Filler (bfiller) said : #3

Wanted to update the status of this. Apport is now enabled by default to generate cores/crash files and I've created a meta package called moblin-debug which will install all of the -dbg versions of moblin packages we currently have (browser, media player, mutter, mutter-moblin, nbtk and clutter).

So it's quite easy now for testers to gather the proper information for crashes. Just do the following:
1) add the dev repos to 8-27 release
deb https://moblin-jaunty-intel:<email address hidden>/moblin-jaunty moblin-jaunty-devel public private
deb-src https://moblin-jaunty-intel:<email address hidden>/moblin-jaunty moblin-jaunty-devel public private

2) sudo apt-get update

3) sudo apt-get install apport moblin-debug

4) reboot

Whenever a crash occurs there will be a .crash file in /var/crash. Just upload the .crash file in the bug and the developer will have all the info to debug.

Can you help with this problem?

Provide an answer of your own, or ask Rusty Lynch for more information if necessary.

To post a message you must log in.