From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1812 invoked by alias); 24 Nov 2003 04:48:48 -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 1804 invoked from network); 24 Nov 2003 04:48:47 -0000 Received: from unknown (HELO ajax.xo.com) (207.155.248.44) by sources.redhat.com with SMTP; 24 Nov 2003 04:48:47 -0000 Received: from MATRICSDBROER (67.105.231.98.ptr.us.xo.net [67.105.231.98]) by ajax.xo.com id XAA10872; Sun, 23 Nov 2003 23:48:46 -0500 (EST) [ConcentricHost SMTP Relay 1.16] From: "Dirk Broer" To: "ECOS" Date: Mon, 24 Nov 2003 04:48:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: [ECOS] Unexpected exception handler call (0x53) X-SW-Source: 2003-11/txt/msg00318.txt.bz2 We are newly targeting an arm based board. We get often an exception with 0x53 (83). Back Trace shows nothing interesting. How best to proceed to track this down? Where would the ‘real’ stack have been stored? Was it stored? My best guess is that this is the default handler, should we override this? Again, can we recover the stack? We are still implementing ‘info threads’ and right now have no direct visibility on the state of other threads in the system. __ __ ___ ________ ___ __ ___ ___ Dirk Broer / ||/ || /_ || /__ __// /__ \\ /// /__ \\ / __\\ //||//||| ///||| /// ///_/// __ /// ||| ///_ ///| //||| /___ || /// /__ // /// /// /__ || /// |// ||| /// ||| /// /// ||| /// ///__/// ____/// /// |||/// |||/// /// ||| /// |____// /____// Software Engineer (410)872-0300 #include #include -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss