site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Nov 9, 2009, at 12:32 PM, Joe Lowe wrote: I am using GDB kernel debugging over ethernet. Whenever I single step over a function call the target system locks up and never returns to the debugger. The keyboard debug break sequence and power button do not help once in this state. The target machine has to be power cycled. Target system is a quad core intel based mac running OSX 10.5.8. The GDB version on the debugger system is "GNU gdb 6.3.50-20050815 (Apple version gdb-966) (Tue Mar 10 02:43:13 UTC 2009)", using the 10.5.8 kernel debug kit. The debugger is fully functional except for the single stepping issue. Has anyone else seen this or have any idea what might be the cause? Joe _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/jamesshimer%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... There are special hardware debugging tools used for debugging schedulers, In Circuit Emulation (ICE) and JTAG. With out them, I think your subject to catch 22 between debugger scheduling and your "step over" break point causing deadlock. This email sent to jamesshimer@mac.com This email sent to site_archiver@lists.apple.com