(start list of debug features) |
(fix template) |
||
Line 7: | Line 7: | ||
For each one: | For each one: | ||
== Template == | == Template == | ||
'''What it does:''' | <br/>'''What it does:''' | ||
'''What is the performance cost:''' | <br/>'''What is the performance cost:''' | ||
'''Bugs found using it:''' | <br/>'''Bugs found using it:''' | ||
'''How to tell if it's turned on:''' | <br/>'''How to tell if it's turned on:''' | ||
TODO: | TODO: |
Revision as of 17:34, 6 May 2010
There's a trade-off to be made between performance and debugging. During the "rawhide" phase where we develop Fedora N+1 it makes sense to turn on some debug features that catch bugs, but which incur performance cost. We can then turn them off whilst polishing the release.
Specific Debug Features
For each one:
Template
What it does:
What is the performance cost:
Bugs found using it:
How to tell if it's turned on:
TODO:
- kernel hooks
- glibc hooks: MALLOC_PERTURB
- any more?
Login message
At terminal
Fedora release 15 (Sesquipedalian) Kernel 2.6.33.3-79.fc13.x86_64 on an x86_64 This is a pre-release version of Fedora, and is running with extra diagnostics that help find bugs, but impact performance. Please read [[DaveMalcolm/DebugSettings]] before attempting to run benchmarks on this system.
How to do this? /etc/issue ?
Graphical desktop
Pop up a dialog with the same text:
+--------------------------------------------------------------------+ | This is a pre-release version of Fedora, and is running with extra | | diagnostics that help find bugs, but impact performance. | | | | Please read [[DaveMalcolm/DebugSettings]] | | before attempting to run benchmarks on this system. | | | | [ ] Don't show this again | | [ OK ] | +--------------------------------------------------------------------+