Difference between revisions of "Debugging Tips"

From eLinux.org
Jump to: navigation, search
(Created page with "* See the Kernel Debugging Tips page * See also Debugging Makefiles * Printk * Debug user-space initialization: ** If you get a panic - "not syncing: Attempted to kil...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 +
* See the [[Debugging_Portal]] page
 
* See the [[Kernel Debugging Tips]] page
 
* See the [[Kernel Debugging Tips]] page
 
* See also [[Debugging Makefiles]]
 
* See also [[Debugging Makefiles]]
* [[Printk]]
+
* [[Debugging by printing]]
 
* Debug user-space initialization:
 
* Debug user-space initialization:
 
** If you get a panic - "not syncing: Attempted to kill init!" it can be for many different reasons. Try setting CONFIG_DEBUG_USER=y in your .config and pass 'user_debug=255' in the kernel command line. That will give you a more verbose output about why user space programs crash. Thanks to Daniel Mack on the linux-arm-kernel mailing list for this tip.
 
** If you get a panic - "not syncing: Attempted to kill init!" it can be for many different reasons. Try setting CONFIG_DEBUG_USER=y in your .config and pass 'user_debug=255' in the kernel command line. That will give you a more verbose output about why user space programs crash. Thanks to Daniel Mack on the linux-arm-kernel mailing list for this tip.
 +
[[Category: Tips and Tricks]]

Latest revision as of 21:37, 3 April 2012

  • See the Debugging_Portal page
  • See the Kernel Debugging Tips page
  • See also Debugging Makefiles
  • Debugging by printing
  • Debug user-space initialization:
    • If you get a panic - "not syncing: Attempted to kill init!" it can be for many different reasons. Try setting CONFIG_DEBUG_USER=y in your .config and pass 'user_debug=255' in the kernel command line. That will give you a more verbose output about why user space programs crash. Thanks to Daniel Mack on the linux-arm-kernel mailing list for this tip.