Re: [ECOS] Difference between CTRLC & BREAK support on GDB stubs

["Rosimildo daSilva" <rosimildo at hotmail dot com>]

>From: Robin Farine <advanc@dial.eunet.ch>
>To: Rosimildo daSilva <rosimildo@hotmail.com>
>CC: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] Difference between CTRLC & BREAK support on GDB stubs
>Date: Tue, 17 Oct 2000 18:27:38 +0200 (CEST)
>
>
>Rosimildo,
>
>The "plf_misc.c" file for the jmr3904 CPU defines 'cyg_hal_user_break()'
>as HAL_BREAKPOINT(breakinst) if neither CYGSEM_HAL_USE_ROM_MONITOR_CygMon
>nor CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is defined.
>

Robin,

You right on it. Our "HAL" was based on tx39/jmr3904. The code
is *almost* the same.


>This installs a breakpoint instruction the GDB stuff will not handle
>specially as it does for the 'breakpoint()' routine, that is, skipping
>one instruction.
>
>I suspect that the code for your platform uses a similar routine and that
>you build without any of the two CPP symbols above defined.

Yes, our application code does not define any of the preprocessor
macros above. HAL_BREAKPOINT(breakinst)is executed.

'cyg_hal_user_break()' is the same as in jmr3904.

I know it must be a very silly thing that I am forgeting to
set, but I have been unable to see what it is.

Any ideas ?

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.