This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Question about GDB response operation on Target. : send again because I didn't get reply due to my email server problem.


hi.
I try to debug my custom board(mpc860 board) through GDB.
I used CVS eCos package and made eCos image including GDB stubs.
but some wierd result happens when program stop by breakpoint.

Passing argument values are not correct. Those looks like a kind of
garbage value.

So I changed option from CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS to
CYGDBG_HAL_DEBUG_CTRLC_SUPPORT in debugging.cdl.

then Passing argument values are CORRECT !!!

that means now i can source-level-debug eCos application with ease.

But I wonder how Target respond to GDB command from Host.
I looked into eCos source about GDB stub related part.
But I'm afraid I could not find where target respond to GDB command.
I mean most of GDB stub related parts are limited with 
" #ifdef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS".

So let me know where(on eCos package source) target respond to GDB
command 
when CYGDBG_HAL_DEBUG_CTRLC_SUPPORT option is used.

thanks in advance.

Tony.




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]