Difference between revisions of "Debugging Tips"
From eLinux.org
Peter Huewe (Talk | contribs) (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...") |
Peter Huewe (Talk | contribs) |
||
| Line 4: | Line 4: | ||
* 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]] | ||
Revision as of 11:39, 28 October 2011
- See the Kernel Debugging Tips page
- See also Debugging Makefiles
- Printk
- 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.
