From Fedora Project Wiki
< Features
(→Scope: initial scope) |
(Complete page) |
||
| Line 9: | Line 9: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/11|Fedora 11]] | ||
* Last updated: January | * Last updated: January 28, 2009 | ||
* Percentage of completion: | * Percentage of completion: 30% | ||
== Detailed Description == | == Detailed Description == | ||
| Line 34: | Line 34: | ||
#* A <code>debuginfofs</code> service, | #* A <code>debuginfofs</code> service, | ||
#* Configuration files to specify the location of the server | #* Configuration files to specify the location of the server | ||
We should also provide a public debuginfofs server for Fedora users, and pre-configure the service to use that. | |||
== How To Test == | == How To Test == | ||
| Line 89: | Line 91: | ||
== User Experience == | == User Experience == | ||
Getting debuginfo to get a backtrace for a bug report will become much, much easier (and faster), but the process will change slightly. | |||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
* A public debuginfofs server will require somewhere around 40GB of disk per Fedora version/arch - a total of 500GB for Fedora (8,9,10) * (i386,x86_64,ppc). | |||
* Some further work could be done to drastically reduce the amount of disk space needed by only unpacking debuginfo ''when it is needed'' - this may be required if the Fedora infrastructure can't spare that much disk space. | |||
* If we need access to the source files as well as the debugging symbols, there will need to be an additional layer on the client-side to find the source files and put them in a place where <code>gdb</code> can find them. | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
None needed - things stay as they are. | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
The gdb info pages and [[Releases/FeatureBuildId]] give some background on the Build-Id feature that makes this possible. | |||
== Release Notes == | == Release Notes == | ||
| Line 105: | Line 116: | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
There is a new <code>debuginfofs</code> service, which provides debuginfo for all Fedora packages over the Internet. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
| Line 110: | Line 123: | ||
* See [[Talk:Features/DebuginfoFS]] | * See [[Talk:Features/DebuginfoFS]] | ||
[[Category: | [[Category:FeatureReadyForWrangler]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Revision as of 22:36, 28 January 2009
Summary
A read-only, internet-mountable filesystem that provides debuginfo (for use with 
gdb
a client service to mount the debuginfo filesystem when needed.
Owner
- Name: Will Woods
- email: wwoods@redhat.com
Current status
- Targeted release: Fedora 11
- Last updated: January 28, 2009
- Percentage of completion: 30%
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
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:
- A
debuginfofs-serverpackage, which provides- A
debuginfofs-serverservice, - Configuration files to specify which distributions (version/arch) to support, and
- Some documentation on setting up / maintaining the server.
- A
- A
debuginfofspackage, which provides- A
debuginfofsservice, - Configuration files to specify the location of the server
- A
We should also provide a public debuginfofs server for Fedora users, and pre-configure the service to use that.
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
Getting debuginfo to get a backtrace for a bug report will become much, much easier (and faster), but the process will change slightly.
Dependencies
- A public debuginfofs server will require somewhere around 40GB of disk per Fedora version/arch - a total of 500GB for Fedora (8,9,10) * (i386,x86_64,ppc).
- Some further work could be done to drastically reduce the amount of disk space needed by only unpacking debuginfo when it is needed - this may be required if the Fedora infrastructure can't spare that much disk space.
- If we need access to the source files as well as the debugging symbols, there will need to be an additional layer on the client-side to find the source files and put them in a place where
gdbcan find them.
Contingency Plan
None needed - things stay as they are.
Documentation
The gdb info pages and Releases/FeatureBuildId give some background on the Build-Id feature that makes this possible.
Release Notes
There is a new debuginfofs service, which provides debuginfo for all Fedora packages over the Internet.