[ECOS] Re: core dump on info->maxfree=maxfree

Jonathan Larmour jlarmour@redhat.com
Wed Nov 28 22:51:00 GMT 2001


shahmilmerchant@aol.com wrote:
> 
> i seem to be compiling fine with my program
> but when i try running the executable for the sample file
> hello
> i get a core dump
> when i run gdb i get the following errors
> Program recieved signal SIGSEV,Segmentation fault
> 0x10000 in _stext ()
> at /opt/ecos/ecos-1.3.1/packages/kernel/v1_3_1/src/common/kapi.cxx:781
> 781  info->maxfree = maxfree
> 
> i read somewhere theres a problem in cyg_mempool_info,but theres no
> workaround I could see.
> Any ideas?

The address it has crashed it is 0x10000. This almost certainly means the
line number it is reporting is a red herring - it's just GDB's best attempt
to find a source line for 0x10000 when there isn't really one.

My guess is that your program entry point is meant to be 0x10000 but you
haven't actually loaded your program into memory yet.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine



More information about the Ecos-discuss mailing list