* [ECOS] How to settle SIGBUS error???
@ 2008-03-19 9:53 grachel
2008-03-19 17:18 ` Andrew Lunn
0 siblings, 1 reply; 3+ messages in thread
From: grachel @ 2008-03-19 9:53 UTC (permalink / raw)
To: ecos-discuss
I encountered a SIGBUS error when I run a phoneMe advanced program on eCos
platform.Because eCos only support one process,I can't kill the process
which encounters the SIGBUS error.Thus,this process will continue reporting
the "Process #42 received signal 10, suspending" over and over again.Then,
how should I do to settle this???Anyone can help me ?????
--
View this message in context: http://www.nabble.com/How-to-settle-SIGBUS-error----tp16141853p16141853.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ECOS] How to settle SIGBUS error???
2008-03-19 9:53 [ECOS] How to settle SIGBUS error??? grachel
@ 2008-03-19 17:18 ` Andrew Lunn
2008-04-08 9:09 ` grachel
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Lunn @ 2008-03-19 17:18 UTC (permalink / raw)
To: grachel; +Cc: ecos-discuss
On Wed, Mar 19, 2008 at 02:37:49AM -0700, grachel wrote:
>
> I encountered a SIGBUS error when I run a phoneMe advanced program on eCos
> platform.Because eCos only support one process,I can't kill the process
> which encounters the SIGBUS error.Thus,this process will continue reporting
> the "Process #42 received signal 10, suspending" over and over again.Then,
> how should I do to settle this???Anyone can help me ?????
Obviously you need to find out why it is accessing memory that does
not exist. Quite likely this is a null point dereference, or maybe you
have overrun your stack. gdb should help you debug your code. Are you
on an ARM? It could also be you are doing none aligned access.
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [ECOS] How to settle SIGBUS error???
2008-03-19 17:18 ` Andrew Lunn
@ 2008-04-08 9:09 ` grachel
0 siblings, 0 replies; 3+ messages in thread
From: grachel @ 2008-04-08 9:09 UTC (permalink / raw)
To: ecos-discuss
Andrew Lunn-2 wrote:
>
> On Wed, Mar 19, 2008 at 02:37:49AM -0700, grachel wrote:
>>
>> I encountered a SIGBUS error when I run a phoneMe advanced program on
>> eCos
>> platform.Because eCos only support one process,I can't kill the process
>> which encounters the SIGBUS error.Thus,this process will continue
>> reporting
>> the "Process #42 received signal 10, suspending" over and over
>> again.Then,
>> how should I do to settle this???Anyone can help me ?????
>
> Obviously you need to find out why it is accessing memory that does
> not exist. Quite likely this is a null point dereference, or maybe you
> have overrun your stack. gdb should help you debug your code. Are you
> on an ARM? It could also be you are doing none aligned access.
>
> 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
>
>
>
Thank you very much,Andrew.I will try it !
--
View this message in context: http://www.nabble.com/How-to-settle-SIGBUS-error----tp16141853p16549564.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-04-08 8:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-19 9:53 [ECOS] How to settle SIGBUS error??? grachel
2008-03-19 17:18 ` Andrew Lunn
2008-04-08 9:09 ` grachel
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).