Re: [ECOS] "hello world" example crashes on synthetic linux target

[Bart Veer <bartv at ecoscentric dot com>]

>>>>> "Tom" == jufi8ni02  <jufi8ni02@sneakemail.com> writes:

    Tom> Folks,

    Tom>   I'm compiling the hello.c example provided with eCos, using
    Tom>   the linux synthetic target (default template).

    Tom> When I run the resulting object, it prints "Hello, eCos
    Tom> world!" then throws core.

    Tom> gdb reports:

    Tom> Program received signal SIGSEGV, Segmentation fault.
    Tom> 0x00000420 in ?? ()
    Tom> (gdb) where
    Tom> #0  0x00000420 in ?? ()
    Tom> #1  0x01003394 in idle_thread_main (data=0)
    Tom>     at /home/spon/Work/RTOS/eCos_from_source_attempt_2/ecos/packages/kernel/current/src/common/thread.cxx:1245
    Tom> #2  0x01003051 in Cyg_HardwareThread::thread_entry (thread=0x0)
    Tom>     at /home/spon/Work/RTOS/eCos_from_source_attempt_2/ecos/packages/kernel/current/src/common/thread.cxx:109
    Tom> #3  0x00000000 in ?? ()

    Tom> Now, I'm aware that this isn't a big problem of itself - who
    Tom> cares if the example program doesn't work? But I'd like to
    Tom> know what's going on here - how do I go about resolving this
    Tom> problem?

Is this with a recent kernel? There has been a change somewhere in the
Linux kernel's signal handling. When the synthetic target's SIGALRM
handler returns back to the Linux kernel it will give a SEGV, like the
above. The same eCos executable running on an older Linux kernel works
fine. I have not yet tracked down exactly what has changed.

Bart

-- 
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss