From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18889 invoked by alias); 12 Apr 2006 20:40:26 -0000 Received: (qmail 18880 invoked by uid 22791); 12 Apr 2006 20:40:26 -0000 X-Spam-Check-By: sourceware.org Received: from sccrmhc13.comcast.net (HELO sccrmhc13.comcast.net) (63.240.77.83) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 12 Apr 2006 20:40:24 +0000 Received: from ultsol.com (c-24-147-245-185.hsd1.ma.comcast.net[24.147.245.185]) by comcast.net (sccrmhc13) with ESMTP id <2006041220402201300242eme>; Wed, 12 Apr 2006 20:40:22 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Apr 2006 20:40:00 -0000 Message-ID: <81C69D96BDD30640952C7A404004AA2543A5A6@ultsol01.tewks.ultsol.local> From: "Fahd Abidi" To: "Andrew Lunn" Cc: X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] Trying to Debug Ecos using GDB X-SW-Source: 2006-04/txt/msg00152.txt.bz2 I'm trying to create a test case where I will use a BDI2000 JTAG emulator to debug the ecos kernel, for that I need an image that has all the symbols built in. I will then strip the executable to create an image that does not have any debug symbols to load onto the target, that way I can debug the kernel thru a JTAG probe. The larger image with debug symbols is used only on the host GDB and the stipped executable sits on the target. Is this possible? Is there any way to tell the linker to leave the debug symbols in place? Thanks, Fahd =20 -----Original Message----- From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn Sent: Wednesday, April 12, 2006 4:30 PM To: Fahd Abidi Cc: ecos-discuss@ecos.sourceware.org Subject: Re: [ECOS] Trying to Debug Ecos using GDB On Wed, Apr 12, 2006 at 04:23:48PM -0400, Fahd Abidi wrote: > Thank you very much for that tip. I used an example hello world=20 > application and linked it to ecos and have an executable image that=20 > can be opened with GDB. >=20 > But now it seems like the executable image only has the symbols built=20 > in for my hello.c program and no other kernel source files are=20 > present. How can I build the application + library so that debug=20 > information for the entire kernel is also present? Why would you want to do that?=20 eCos is designed for embedded systems where memory is short. So linking to the application leaves out everything that is not used. Andrew --=20 Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss