This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: RE: SIGTRAP problem.
- To: "Trenton D. Adams" <tadams at extremeeng dot com>
- Subject: RE: [ECOS] RE: SIGTRAP problem.
- From: Cristiano Ligieri Pereira <cpereira at ics dot uci dot edu>
- Date: Wed, 1 Aug 2001 14:23:42 -0700 (PDT)
- cc: 'eCos Discussion' <ecos-discuss at sourceware dot cygnus dot com>
The source of the problem was varying but mostly in the eCos code. I was
playing with the core frequency of the processor the cause of the problem
was that the memory was getting inaccessible.
I don't thing it helps you on solving your problem, but at least give you
an idea on what might cause a SIGTRAP.
Cristiano.
------------------------------------------------------------
Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira
On Wed, 1 Aug 2001, Trenton D. Adams wrote:
> Did yours happen in one of your functions, or inside a function in eCos?
>
> Mine is happening in accept (). Is that where yours happened?
>
> > -----Original Message-----
> > From: Cristiano Ligieri Pereira [mailto:cpereira@ics.uci.edu]
> > Sent: Wednesday, August 01, 2001 3:06 PM
> > To: Trenton D. Adams
> > Cc: eCos Discussion
> > Subject: Re: [ECOS] RE: SIGTRAP problem.
> >
> >
> > I've got the same error message some time ago and was wondering the
> same
> > thing. Here is what Gary Thomas replied me:
> >
> > > What's the exact meaning of this [error] message?
> > >
> > > "Program received signal SIGTRAP, Trace/breakpoint trap.
> > > 0x62160 in some_function ()"
> > >
> > > Is it an error in my application? If not, can I avoid (by doing
> some
> > > configuration) having it stopping my application.
> > >
> >
> > It definitely is in you application. Since eCos is designed for
> > embedded
> > use, it makes no sense [normally] to go on if such a thing happens,
> as
> > this is often quite serious. You'll have to debug your application
> and
> > fix it, sorry.
> >
> > > PS: It comes out from the Compaq Ipaq running eCos. I'm using the
> > serial
> > > port to debug it and see the messages.
> >
> > I'd guess it means that the program ran away and ended up executing
> > garbage.
> >
> > Basically, the error means that there was some sort of execution
> > error - probably an illegal instruction.
> >
> > First thing would be to use GDB and see if you can get a backtrace.
> > Then you can figure out how it got there.
> >
> > ------------------------------------------------------------
> > Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira
> >
>
>
>