From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30990 invoked by alias); 15 Oct 2003 20:59:31 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 30975 invoked from network); 15 Oct 2003 20:59:29 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sources.redhat.com with SMTP; 15 Oct 2003 20:59:29 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1A9sh2-0007OZ-00; Wed, 15 Oct 2003 22:56:28 +0200 Date: Wed, 15 Oct 2003 20:59:00 -0000 To: adrian@atheros.com Cc: eCos Disuss Message-ID: <20031015205628.GB1165@lunn.ch> Mail-Followup-To: adrian@atheros.com, eCos Disuss Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i From: Andrew Lunn Subject: [ECOS] Re: does ecos support generating core files of kernel crashdumps? X-SW-Source: 2003-10/txt/msg00270.txt.bz2 Hi Adrian There are a couple things you can do to help in field debugging. 1) Hook into the cyg_assert_fail() function and write the text of the message to flash, syslog, ide device etc 2) Hook into the exception handler and print/flash/syslog all the saved registers and maybe some of the stack. If you can read assembly language and match it back to the C sources, i found the register dump very useful. I've solved, or at least got a good head start fixing in field bugs with this. Andrew -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss