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: jskov at redhat dot com
- Subject: Re: [ECOS] Difference between CTRLC & BREAK support on GDB stubs
- From: "Rosimildo daSilva" <rosimildo at hotmail dot com>
- Date: Mon, 16 Oct 2000 22:35:50 CDT
- Cc: ecos-discuss at sourceware dot cygnus dot com
>From: Jesper Skov <jskov@redhat.com>
>To: "Rosimildo daSilva" <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] Difference between CTRLC & BREAK support on GDB stubs
>Date: 16 Oct 2000 08:35:11 +0200
>
>
>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.
>
Jesper, thanks for your help...
You are absolutely right. This is the behavior that I am seeing.
But, the "breakpoint" reached is inside of the "ctrlc_isr",
so the same "line number, file name" is reported. I'd like to
change that behavior and add the breakpoint to the address
of the interrupted routine.
Rosimildo.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.