This is the mail archive of the ecos-discuss@sourceware.org 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]
Other format: [Raw text]

Re: Can "redboot + gdb stub" debug an application that has its own vector?

On Wed, Oct 29, 2008 at 09:36:11AM +0800, Fu-Yuan Lee wrote:
> Thanks a lot.
> 
> Can you please kindly hints us a little more on this part?
> 
> The vector part (from address 0x20 to 0x3C) are always changed when we load
> a new application (ELF file) using the "load" gdb command. And after that we
> failed to enter gdb-stub. So is the solution to keep some redboot's
> vector pointers
> (e.g. undefined_instruction, software_interrupt, abort_data...) ?

It sounds like you have somehthing wrong with the configuration of
your application. It should not be modifying these vectors. Take a
look at 

packages/hal/arm/arch/current/src/vectors.S

Depending on the values of CYG_HAL_STARTUP_RAM and
CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS it will or will not change the
vectors.

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]