Hi Habeeb, You can debug deeper and try to single step in _Linker_set__Sysinit_rtems_libio_post_driver function and see where it fails. Also building with -O0 might help until you are sure it's working, you can re-enable optimization. Regarding the stack, there is a CONFIGURE_STACK_CHECKER_ENABLED option that you can add, I sometimes found it useful to catch stack corruption.
On Wed, Jun 8, 2016 at 4:47 AM, Olufowobi, Habeeb <habeeb.olufow...@bison.howard.edu> wrote: > Hi, > > I have been able to build my new BSP and currently trying run HelloWorld > with OpenOCD and gdb. > > Following is the error message I'm getting when I run hello.exe and not sure > how to debug this error. > > Any idea about this issue and how to debug it? > > #0 0x000047ee in _Terminate ( > the_source=the_source@entry=RTEMS_FATAL_SOURCE_EXCEPTION, > is_internal=is_internal@entry=false, the_error=536874968) > at > ../../../../../../../rtems.git/c/src/../../cpukit/score/src/interr.c:52 > #1 0x00003d16 in rtems_fatal ( > source=source@entry=RTEMS_FATAL_SOURCE_EXCEPTION, > error=<optimized out>) > at > ../../../../../../../rtems.git/c/src/../../cpukit/sapi/src/fatal2.c:34 > #2 0x0000786e in _ARM_Exception_default (frame=<optimized out>) > at > ../../../../../../../../../rtems.git/c/src/../../cpukit/score/cpu/arm/arm-exception-default.c:24 > #3 <signal handler called> > #4 0x00000000 in bsp_start_vector_table_begin () > #5 0x0000f2d0 in _Linker_set__Sysinit_rtems_libio_post_driver () > Backtrace stopped: previous frame identical to this frame (corrupt stack?) > > Regards, > Habeeb -- Hesham _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
