From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 77025 invoked by alias); 20 Nov 2019 13:18:53 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 76744 invoked by uid 48); 20 Nov 2019 13:18:48 -0000 From: "mark at klomp dot org" To: elfutils-devel@sourceware.org Subject: [Bug libdw/25173] dwarf_getsrc_die fails for rust code Date: Wed, 20 Nov 2019 13:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: libdw X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2019-q4/txt/msg00193.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25173 --- Comment #8 from Mark Wielaard --- (In reply to Milian Wolff from comment #7) > hmm but in perfparser we have a workaround for missing aranges... I'll ha= ve > to dig into this to see why it doesn't work here. You also mention it is an issue with dwarf_getsrc_die in the subject. Which would indicate that it is some other issue, because when you call dwarf_getsrc_die you already would have found the DIE (by address). So mayb= e it is something else in your case? BTW. I do agree it would be nice if libdw handled missing debug_aranges. The problem is simply that you cannot know the difference between missing and n= ot covered. Which means that for any address lookup that doesn't match an aran= ge you would have to do some fallback lookup, which could be expensive. So sti= ll pondering how to handle this without penalizing debug files that do have correct and complete aranges (maybe we could just handle the case where the= re are just no .debug_aranges at all, and only then make some fallback code k= ick in?) --=20 You are receiving this mail because: You are on the CC list for the bug.