From: Andrew Lunn <andrew@lunn.ch>
To: grachel <grachel1986@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] How to settle SIGBUS error???
Date: Wed, 19 Mar 2008 17:18:00 -0000 [thread overview]
Message-ID: <20080319095541.GA27494@lunn.ch> (raw)
In-Reply-To: <16141853.post@talk.nabble.com>
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
next prev parent reply other threads:[~2008-03-19 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 9:53 grachel
2008-03-19 17:18 ` Andrew Lunn [this message]
2008-04-08 9:09 ` grachel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080319095541.GA27494@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=grachel1986@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).