From Fedora Project Wiki
(→‎How To Test: simple test run)
(→‎Scope: initial scope)
Line 25: Line 25:
== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
There will be two main parts to this feature:
# A <code>debuginfofs-server</code> package, which provides
#* A <code>debuginfofs-server</code> service,
#* Configuration files to specify which distributions (version/arch) to support, and
#* Some documentation on setting up / maintaining the server.
# A <code>debuginfofs</code> package, which provides
#* A <code>debuginfofs</code> service,
#* Configuration files to specify the location of the server


== How To Test ==
== How To Test ==

Revision as of 22:23, 28 January 2009

Summary

A read-only, internet-mountable filesystem that provides debuginfo (for use with Package-x-generic-16.pnggdb and other debugging tools), and

a client service to mount the debuginfo filesystem when needed.

Owner

Current status

  • Targeted release: Fedora 40
  • Last updated: January 22, 2009
  • Percentage of completion: 10%

Detailed Description

When a program crashes or is otherwise misbehaving, one of the most helpful things to put in a bug report is a traceback of the offending process, gathered by using Package-x-generic-16.pnggdb. GNOME's Package-x-generic-16.pngbug-buddy does this automatically. But without debugging info, the tracebacks are incomplete.

debuginfo-install can be used to install the needed debuginfo packages, but this takes a long time (2-5 minutes) and 95% of the installed data is unused.

This Feature will provide scripts and tools to provide a WebDAV filesystem containing all the debuginfo needed for everything in Fedora, and a service to allow users (or automatic crash-reporting processes - like Features/CrashCatcher) to mount the filesystem when needed.

Benefit to Fedora

By simplifying the process of getting debugging info, we can improve the quality of bug reports, which should make it easier (and faster) to get bugs fixed.

Scope

There will be two main parts to this feature:

  1. A debuginfofs-server package, which provides
    • A debuginfofs-server service,
    • Configuration files to specify which distributions (version/arch) to support, and
    • Some documentation on setting up / maintaining the server.
  2. A debuginfofs package, which provides
    • A debuginfofs service,
    • Configuration files to specify the location of the server

How To Test

1. Prepare a debuginfo server

  • Instructions / public instance coming soon

2. Install debuginfofs

  • git repo / packages coming soon

3. Mount debuginfofs

sudo service debuginfofs start

4. Crash a program in gdb

[wwoods@metroid debuginfofs]$ gdb $(which sleep)
GNU gdb Fedora (6.8-29.fc10)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
(gdb) set args 999
(gdb) run
Starting program: /bin/sleep 999
[Hit Ctrl-C]
Program received signal SIGINT, Interrupt.
__kernel_vsyscall () at arch/x86/vdso/vdso32/int80.S:16
16	arch/x86/vdso/vdso32/int80.S: No such file or directory.
	in arch/x86/vdso/vdso32/int80.S
Current language:  auto; currently asm
(gdb) bt
#0  __kernel_vsyscall () at arch/x86/vdso/vdso32/int80.S:16
#1  0x008ac430 in __nanosleep_nocancel () from /lib/libc.so.6
#2  0x0804abd3 in xnanosleep (seconds=999) at xnanosleep.c:112
#3  0x080490f6 in main (argc=2, argv=0xbffff514) at sleep.c:150
(gdb)

If everything is working as expected, you will see the function/file names, as above.


User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion