From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17963 invoked by alias); 15 Oct 2003 20:43:57 -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 17956 invoked from network); 15 Oct 2003 20:43:56 -0000 Received: from unknown (HELO hermes.chez-thomas.org) (63.225.98.241) by sources.redhat.com with SMTP; 15 Oct 2003 20:43:56 -0000 Received: by hermes.chez-thomas.org (Postfix, from userid 2000) id 6B94650E0ED; Wed, 15 Oct 2003 14:43:56 -0600 (MDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by hermes.chez-thomas.org (Postfix) with ESMTP id ED89450E0EC; Wed, 15 Oct 2003 14:43:54 -0600 (MDT) From: Gary Thomas To: Adrian Caceres Cc: ecos-discuss@sources.redhat.com In-Reply-To: <3F8DB002.9090800@atheros.com> References: <3F8D83CF.5090609@atheros.com> <1066241316.32461.66.camel@hermes> <3F8DB002.9090800@atheros.com> Content-Type: text/plain Organization: MLB Associates Message-Id: <1066250632.32461.89.camel@hermes> Mime-Version: 1.0 Date: Wed, 15 Oct 2003 20:43:00 -0000 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_XIMIAN autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: [ECOS] does ecos support generating core files or kernel crash dumps? X-SW-Source: 2003-10/txt/msg00269.txt.bz2 On Wed, 2003-10-15 at 14:37, Adrian Caceres wrote: > Many embedded systems have a local/ide type bus > to a flash. Assuming the basic driver to such interface was not affected > by the crash, it would be possible to write a dump to it. > Or there might be some storage available across some network > interface. The embedded system > could send the crash dump over to the other end for storage. > > Having gdb support is great for development, but when it comes > to beta, a core dump can be more useful. It is not rare for > a specific problem to only occur at some beta site and there > is simply no way to gdb to it. The serial port might not even > be stuffed or accesible in these units. But give them a unit > with an extra large flash, wait for the problem to happen again, > get the unit back, and now you might have all the information you need. > If the embedded device already has a removable flash such > as a digital or video camera, the process is simply a swap of > a flash. > These are wonderful arguments (I made the same ones more than 25 years ago to my boss at the time...). The infrastructure is all there for you to add such a capability, it's just not something that has ever been done before. As for your first statement about having a local IDE bus with FLASH - that's probably less than 2% of all of the systems that eCos is normally deployed on, but if you've got it, flaunt it! > - adrian > > Gary Thomas wrote: > > >On Wed, 2003-10-15 at 11:28, Adrian Caceres wrote: > > > > > >>I am wondering if ecos already supports generating core files or crash > >>dumps for post-mortem analysis using gdb. > >> > >> > > > >No. Where would you put them [in an embedded system]? > > > >If the application "crashes", just connect to it using GDB > >and figure out why. > > > > > > -- Gary Thomas MLB Associates -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss