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: Tue, 17 Oct 2000 09:31:01 +0200 (CEST)
- Cc: jskov at redhat dot com, ecos-discuss at sourceware dot cygnus dot com
- References: <F1489Lv40q2HxHr4h1L00006432@hotmail.com>
>>>>> "Rosimildo" == Rosimildo daSilva <rosimildo@hotmail.com> writes:
Rosimildo> You are absolutely right. This is the behavior that I am
Rosimildo> seeing. But, the "breakpoint" reached is inside of the
Rosimildo> "ctrlc_isr", so the same "line number, file name" is
Rosimildo> reported. I'd like to change that behavior and add the
Rosimildo> breakpoint to the address of the interrupted routine.
When I look at the vrc4373 platform HAL in the 1.3.1 release code, I
see that it relies on stubs (in cyg_hal_user_break) to do the
magic. Is that your problem? Have you enabled
CYGSEM_HAL_USE_ROM_MONITOR_GDB_stubs and do you actually have a stub
in place which does the right thing?
Jesper