From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Tue, 12 Feb 2013 12:02:43 -0500 Subject: [U-Boot] [U-boot]-gdwarf option In-Reply-To: <1360611812.8517.4@snotra> References: <20130205154819.DD5E7200556@gemini.denx.de> <1360611812.8517.4@snotra> Message-ID: <20130212170243.GB26121@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Feb 11, 2013 at 01:43:32PM -0600, Scott Wood wrote: > On 02/07/2013 02:01:05 AM, TigerLiu at viatech.com.cn wrote: > >Hi, experts: > >I have a JTAG debugger. > >Its manual suggested user should add "-gdwarf-2" option in the arm gcc > >compiler. > >Because it could produce debugging information. > > > >But I searched the whole uboot source package, could not find > >"-gdwarf-2" option in config.mk or other files. > > > >Why? > > I think it's already the default with most toolchains. Do you see > any difference in the output when supplying that flag? Indeed. For most common values of gcc versions, using -g will pick the "best" choice for debug information and this will be DWARF2 information already. There is no need to specify -gdwarf-2 (or similar). -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: