* [ECOS] core dump on info->maxfree=maxfree
@ 2001-11-12 5:32 shahmilmerchant
2001-11-20 18:28 ` [ECOS] " Jonathan Larmour
0 siblings, 1 reply; 3+ messages in thread
From: shahmilmerchant @ 2001-11-12 5:32 UTC (permalink / raw)
To: ecos-discuss; +Cc: jlarmour
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?
Shahmil
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ECOS] Re: core dump on info->maxfree=maxfree
2001-11-12 5:32 [ECOS] core dump on info->maxfree=maxfree shahmilmerchant
@ 2001-11-20 18:28 ` Jonathan Larmour
2001-11-28 22:51 ` Jonathan Larmour
0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Larmour @ 2001-11-20 18:28 UTC (permalink / raw)
To: shahmilmerchant; +Cc: ecos-discuss
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ECOS] Re: core dump on info->maxfree=maxfree
2001-11-20 18:28 ` [ECOS] " Jonathan Larmour
@ 2001-11-28 22:51 ` Jonathan Larmour
0 siblings, 0 replies; 3+ messages in thread
From: Jonathan Larmour @ 2001-11-28 22:51 UTC (permalink / raw)
To: shahmilmerchant; +Cc: ecos-discuss
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-11-29 6:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-11-12 5:32 [ECOS] core dump on info->maxfree=maxfree shahmilmerchant
2001-11-20 18:28 ` [ECOS] " Jonathan Larmour
2001-11-28 22:51 ` Jonathan Larmour
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).