This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Difference between CTRLC & BREAK support on GDB stubs
- To: "Rosimildo daSilva" <rosimildo at hotmail dot com>
- Subject: Re: [ECOS] Difference between CTRLC & BREAK support on GDB stubs
- From: Jesper Skov <jskov at redhat dot com>
- Date: 16 Oct 2000 08:35:11 +0200
- Cc: ecos-discuss at sourceware dot cygnus dot com
- References: <F189vBcN7DaJHFzrK0p00003949@hotmail.com>
>>>>> "Rosimildo" == Rosimildo daSilva <rosimildo@hotmail.com> writes:
Rosimildo> Hi, Could anyone explain the difference between CTRLC and
Rosimildo> BREAK support in the GDB stubs ?
Jonathan already did. But I'd like to add that eventually the BREAK
option will go away as all targets are changed to support the new
virtual vector magic.
In 1.3.1/MIPS you want to look at hal_default_isr in
mips/arch/.../src/hal_misc.c.
Ctrl-c support work by enabling the serial receive interrupt, but not
attach any handler. If a serial RX interrupt reaches the
hal_default_isr() it will be recognized as such and a breakpoint will
be inserted at the PC of the interrupted function.
The behavior you saw is probably caused by the receive interrupt not
being enabled - then some old code in hal_diag.c catches the GDB
ctrl-c character the next time the target outputs a line of text.
Jesper