This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Ctrl-c problem
Sure, it's possible. You should probably have console and KGDB
configured for different ports...
In any case, not a GDB bug.
On Mon, Dec 02, 2002 at 12:02:07PM -0500, Richard Brunelle wrote:
> I tried echoing '\003' and I still can't stop it.
>
> I'm wondering if the problem doesn't come when the boot resumed. After
> the boot procedure is completed, is there a chance that the serial port
> used on the target machine be re-configured to a different baud rate?
>
> Daniel Jacobowitz wrote:
>
> >Then it should work if you are using any current KGDB patch. You can
> >try echoing '\003' out the serial port (echo '\003' > /dev/ttyS0) and
> >see if that stops it.
> >
> >On Mon, Dec 02, 2002 at 11:17:17AM -0500, Richard Brunelle wrote:
> >
> >
> >>My target platform is a x86 single board computer running a PentiumMMX @
> >>266 MHz.
> >>Its seen as a standard PC with extra hardware on it (analog to digital
> >>converter).
> >>
> >>Daniel Jacobowitz wrote:
> >>
> >>
> >>
> >>>On Fri, Nov 29, 2002 at 04:07:14PM -0500, Richard Brunelle wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I'm doing kernel debugging through the use of gdb running on a
> >>>>development machine and a gdb stub running on a target machine. The
> >>>>latter is acheive with the kgdb patch applied to a kernel 2.4.18. This
> >>>>patch allows me to connect a development PC to a target PC through a
> >>>>serial line. It allows me to remotely debug a patched kernel. The
> >>>>connection works fine, I'm able to connect gdb to the target machine at
> >>>>boot time (target remote /dev/tyS0). The problem is not hardware. I am
> >>>>able to step in the kernel code at this time. After a few step, I
> >>>>resume the execution of the kernel with the continue command.
> >>>>
> >>>>My problem comes when I want to stop the execution of the target kernel
> >>>>with gdb. Usually Ctrl-c is used to stop the execution of the running
> >>>>process. So I hit Ctrl-c but the kernel never stop.
> >>>>
> >>>>Is there any configuration for gdb to enable Ctrl-c?
> >>>>
> >>>>Does anyone ever experience this problem?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>What's your target platform? C-c works using the x86 KGDB stub. I
> >>>don't know if it works on PowerPC, and it definitely doesn't work on
> >>>MIPS. This is a stub question.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
>
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer