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 --- Solved.
- To: ecos-discuss at sourceware dot cygnus dot com
- Subject: Re: [ECOS] Difference between CTRLC & BREAK support on GDB stubs --- Solved.
- From: "Rosimildo daSilva" <rosimildo at hotmail dot com>
- Date: Sat, 21 Oct 2000 09:22:23 CDT
>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: 18 Oct 2000 10:29:15 +0200
>
>It uses the hal_vsr_table to find the address of a function (in ROM!)
>that will set the breakpoint. If you don't have a stub in ROM, that
>will obviously not work.
>
>The first alternative is to include stubs in the application image by
>enabling CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS. In that case the stub
>code will realize that the break instruction in breakpoint() was hit,
>and will increment the address when continuing.
I have used the idea of a "hal_virtual_vector_table" used on the Vr4300
variant, and added a function to call the stub to set the
breakpoint. Now, everything works.
Thanks, to all that helped me.
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.