The difficulty is that the code in single step entry should make sure there is no difference for application debugging even when kgdb is enabled.
Sonic -----Original Message----- From: Jie Zhang [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 11:59 AM To: Zhang, Sonic Cc: Bernd Schmidt; [email protected]; uclinux-dist-devel Subject: Single stepping issue for KGDB Let's move to the development mailing lists. Zhang, Sonic wrote: > I am trying to figure out a proper solution for both gdb and kgdb now. > Maybe Bernd can give out an explanation on what his commit r4673 want > to do? At least that commit prevent any possibility from trapping into > single step in kernel code. > As my understand, Bernd's change was trying to get things right for application debugging. But he might not notice that there were several lines of code mixed in ex_single_step were not for application debugging, but for KGDB. I think KGDB specific code should be enclosed by CONFIG_KGDB, thus it will not add overheads when KGDB is not configured. It will be clear for reader to see which lines are for KGDB. Jie _______________________________________________ Toolchain-devel mailing list [email protected] http://blackfin.uclinux.org/mailman/listinfo/toolchain-devel
