RE: [ECOS] RE: SIGTRAP problem.

["Trenton D. Adams" <tadams@extremeeng.com>]

I apologize.  That's the last time I ask a question on the list when I
stayed up playing computer games the night before!!!

I'm a complete moron.  I was trying to accept a connection on a variable
that I hadn't even initialized.

Anyhow, I suppose sleep would be a good thing right about now.

  > -----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
  >