* Ctrl-c problem @ 2002-11-29 13:09 Richard Brunelle 2002-12-01 13:35 ` Daniel Jacobowitz 0 siblings, 1 reply; 7+ messages in thread From: Richard Brunelle @ 2002-11-29 13:09 UTC (permalink / raw) To: gdb 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? Richard Brunelle ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ctrl-c problem 2002-11-29 13:09 Ctrl-c problem Richard Brunelle @ 2002-12-01 13:35 ` Daniel Jacobowitz 2002-12-02 8:20 ` Richard Brunelle 0 siblings, 1 reply; 7+ messages in thread From: Daniel Jacobowitz @ 2002-12-01 13:35 UTC (permalink / raw) To: Richard Brunelle; +Cc: gdb 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ctrl-c problem 2002-12-01 13:35 ` Daniel Jacobowitz @ 2002-12-02 8:20 ` Richard Brunelle 2002-12-02 8:25 ` Daniel Jacobowitz 0 siblings, 1 reply; 7+ messages in thread From: Richard Brunelle @ 2002-12-02 8:20 UTC (permalink / raw) To: Daniel Jacobowitz; +Cc: gdb 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. > > > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ctrl-c problem 2002-12-02 8:20 ` Richard Brunelle @ 2002-12-02 8:25 ` Daniel Jacobowitz 2002-12-02 9:05 ` Richard Brunelle 0 siblings, 1 reply; 7+ messages in thread From: Daniel Jacobowitz @ 2002-12-02 8:25 UTC (permalink / raw) To: Richard Brunelle; +Cc: gdb 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ctrl-c problem 2002-12-02 8:25 ` Daniel Jacobowitz @ 2002-12-02 9:05 ` Richard Brunelle 2002-12-02 9:18 ` Daniel Jacobowitz 0 siblings, 1 reply; 7+ messages in thread From: Richard Brunelle @ 2002-12-02 9:05 UTC (permalink / raw) To: Daniel Jacobowitz; +Cc: gdb 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. >>> >>> >>> >>> >>> >> >> >> > > > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ctrl-c problem 2002-12-02 9:05 ` Richard Brunelle @ 2002-12-02 9:18 ` Daniel Jacobowitz 2002-12-02 9:27 ` Richard Brunelle 0 siblings, 1 reply; 7+ messages in thread From: Daniel Jacobowitz @ 2002-12-02 9:18 UTC (permalink / raw) To: Richard Brunelle; +Cc: gdb 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Ctrl-c problem 2002-12-02 9:18 ` Daniel Jacobowitz @ 2002-12-02 9:27 ` Richard Brunelle 0 siblings, 0 replies; 7+ messages in thread From: Richard Brunelle @ 2002-12-02 9:27 UTC (permalink / raw) To: Daniel Jacobowitz; +Cc: gdb That was the problem. You are right, miss-configuration problem, not a gdb bug. Daniel Jacobowitz wrote: >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. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2002-12-02 17:27 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2002-11-29 13:09 Ctrl-c problem Richard Brunelle 2002-12-01 13:35 ` Daniel Jacobowitz 2002-12-02 8:20 ` Richard Brunelle 2002-12-02 8:25 ` Daniel Jacobowitz 2002-12-02 9:05 ` Richard Brunelle 2002-12-02 9:18 ` Daniel Jacobowitz 2002-12-02 9:27 ` Richard Brunelle
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox