This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: eCos crash log
- From: "Retallack, Mark (Poole)" <mark dot retallack at siemens dot com>
- To: "'Scott Wilkinson'" <scott at alliantnetworks dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Thu, 5 Jun 2003 08:23:16 +0100
- Subject: RE: [ECOS] eCos crash log
This is a GDB packet. It should be possible to decode it.
See Section "3.5. Packet Formats" in:
http://world.std.com/~qqi/download/protocol.txt
>From what i remember, 00050840 or 00087650 is the location of the
instruction that caused the crash (in hex i think).
-----Original Message-----
From: Scott Wilkinson [mailto:scott@alliantnetworks.com]
Sent: Thursday 05 June 2003 03:36 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] eCos crash log
It appears that eCos prints some information in a dying gasp if it
crashes (well, sometimes but not always). Is this format documented
anywhere?
Below is an example. BTW - I am running the tm_basic test application.
$T0b40:00050840;01:00087650;#c0
Thanks,
Scott
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Siemens Traffic Controls is a division of Siemens plc. Registered No.
727817, England.
Registered office: Siemens House, Oldbury, Bracknell, Berkshire, RG12 8FZ.
This communication contains information which is confidential and
may also be privileged. It is for the exclusive use of the addressee.
If you are not the addressee please note that any distribution,
reproduction, copying, publication or use of this communication
or the information in it is prohibited. If you have received this
communication in error, please contact us immediately and also
delete the communication from your computer.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss