From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 380 invoked by alias); 22 Jan 2013 20:11:44 -0000 Received: (qmail 358 invoked by uid 48); 22 Jan 2013 20:11:43 -0000 From: "jkain at nvidia dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/15032] GNU/Linux backtrace fails to use eh_frame information when built with --enable-64-bit-bfd Date: Tue, 22 Jan 2013 20:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jkain at nvidia dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2013-q1/txt/msg00111.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=15032 --- Comment #7 from Joseph Kain 2013-01-22 20:11:41 UTC --- > > as I was in the process of adding missing .eh_frame data > I believe the problem is in your added data. How do you add it? I just added by adding the -fasynchronous-unwind-tables to my gcc invocations. Looking over the gcc source I see that for non-PIC builds gcc doesn't include the 'R' augmentation at all. However, ld adds it when linking my objects together. I'm using binutils 2.18 which includes a bfd that uses encoding 0x10 (DW_EH_PE_pcrel). Newer binutil release's bfds use 0x1b (DW_EH_PE_pcrel | DW_EH_PE_sdata4). So, is it the case that gdb doesn't support binaries built with binutils 2.18? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.