Re: kgdb doesn't respond to Ctrl+C

["Amit S. Kale" <amitkale@emsyssoft.com>]

Works for me too now. Looks like a false alarm

-Amit

On Tuesday 23 Mar 2004 8:55 pm, Tom Rini wrote:
> On Tue, Mar 23, 2004 at 12:02:30PM +0530, Amit S. Kale wrote:
> > I guess something's gone wrong with serial port interrupts.
> >
> > Tom, any ideas?
>
> Current CVS works for me.  Relevant .config section:
> #
> # Kernel hacking
> #
> CONFIG_DEBUG_KERNEL=y
> CONFIG_EARLY_PRINTK=y
> # CONFIG_DEBUG_STACKOVERFLOW is not set
> # CONFIG_DEBUG_STACK_USAGE is not set
> # CONFIG_DEBUG_SLAB is not set
> # CONFIG_DEBUG_IOVIRT is not set
> CONFIG_MAGIC_SYSRQ=y
> # CONFIG_DEBUG_SPINLOCK is not set
> # CONFIG_DEBUG_PAGEALLOC is not set
> # CONFIG_DEBUG_HIGHMEM is not set
> CONFIG_DEBUG_INFO=y
> # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
> CONFIG_KGDB=y
> CONFIG_KGDB_8250=y
> # CONFIG_PPC_SIMPLE_SERIAL is not set
> CONFIG_KGDB_SIMPLE_SERIAL=y
> CONFIG_KGDB_9600BAUD=y
> # CONFIG_KGDB_19200BAUD is not set
> # CONFIG_KGDB_38400BAUD is not set
> # CONFIG_KGDB_57600BAUD is not set
> # CONFIG_KGDB_115200BAUD is not set
> CONFIG_KGDB_TTYS0=y
> # CONFIG_KGDB_TTYS1 is not set
> # CONFIG_KGDB_TTYS2 is not set
> # CONFIG_KGDB_TTYS3 is not set
> CONFIG_FRAME_POINTER=y
> CONFIG_X86_FIND_SMP_CONFIG=y
> CONFIG_X86_MPPARSE=y