From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5573 invoked by alias); 26 Mar 2018 19:25:04 -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 5428 invoked by uid 89); 26 Mar 2018 19:24:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99.4 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=Hx-languages-length:1439 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mout.gmx.net Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.19) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 26 Mar 2018 19:24:46 +0000 Received: from [192.168.2.99] ([2.204.109.240]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MWBpJ-1f2RVx1vEv-00XLc1; Mon, 26 Mar 2018 21:24:32 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Read .debug_line without .debug_info From: Torsten Polle In-Reply-To: <20180326191201.GC9061@wildebeest.org> Date: Mon, 26 Mar 2018 19:25:00 -0000 Cc: Sasha Da Rocha Pinheiro , "elfutils-devel@sourceware.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180326191201.GC9061@wildebeest.org> To: Mark Wielaard X-Mailer: Apple Mail (2.3445.5.20) X-Provags-ID: V03:K0:LMr3IWkWtGuvC+rRRxPQcrWqIMx3E0/4da47Gl37/OAwJjs5hje UuTELe6Ga4HvS0W8t/6J5bLSnnOY8f8uuHIo0vTdC0b4ET7RHmyRhjbgVH9MNegQPAHb4Dn BCgK9zZXwv5RgHJGPHrxur0KF3wXElm+g8zGmUSkcA0JzFHCAV1pX3RYvoS4R/Ve7a7lnYe icyM2msiOerJKnYK8hTZw== X-UI-Out-Filterresults: notjunk:1;V01:K0:MRSb0IPDRWQ=:Z2FpRRD+dMqgY3iJ4VdcpP Beljl5klB9r60TbhOgv7jfQxN0GsgpgFyYFkEz6IGywy1lkDvPKxilRlDFhwtqrqSuPufiMHK qIY7NiqG0fGzhOwfot/z8xU0dnxn3ZcMtJ27JshnY4FHEOnd+9pWjMMMbdo98iUFZsTIJUd3I CvUwABWZqX4Vfw1VSZKbdrARzXPtetDdK0Ud+dn6AkaVMRGNYudDQuA+zV6qp80MVhg8o1AQN 7VBnv4O5JwBqoNby4tXwHdaerzpVtOXX11NrbnY+Sl/HdfREPPA0R9rmuKpmaEbcHhqDso0Uh syWBD1FOCGmO71yOjfoKd2dGr+njGGfozSchGfOV974cciGVeqcA1179WCYFWOXqXUFr9frvR DtOWtfM8rCpukvefqZd7QEjzH1NH6EYVflzyoaIYghZvXQin2nd/AsBuEsLoe5HTZHNgNb3Sl fcCVeDaJtSPU1SAMog5IzeAZE8z/lnUlmwr0FC4H9xaP7yO+kRxEipDU9dpbBQM1G8YhR50ZU nm8oFbd5Or5FRZDfsRlZRvsfQBZ6+LYxGmzN19cBCNyikUcZHLhhQ2bl99b9eXQ2UVS+9eLRD 3lTQ6aIvybIbZh1S7OiKh2bkx8djoiBVbcs4Upoeh8iJDw3fE1V09Ev7WE/6hz8pCM76aR18n KF0YwH0PTkdYqQTqTeJRUY/qslb4q1Rwtfb1xECYMJdprML0do79VDf5GLYRAP5h6V4DWjuN0 Jief/K7s2uWivcLvBWuWahjASdYGUahE6xDCbzw8s3enPimZP/8dU0z2DsNRA0w4W0/I2oL+6 JUNhJRAoK4+6ebeVNUGk8GYOPqi5wJliVIHS8t6j04fb/fL8vw= X-IsSubscribed: yes X-SW-Source: 2018-q1/txt/msg00111.txt.bz2 Hi Mark, > Am 26.03.2018 um 21:12 schrieb Mark Wielaard : >=20 > Hi Sasha, >=20 > On Mon, Mar 26, 2018 at 04:41:06PM +0000, Sasha Da Rocha Pinheiro wrote: >> is it possible to read contents of .debug_line section without the >> presence of a .debug_info section? >=20 > No, because .debug_line sections need some information from the CU > which comes from the .debug_info. In particular the directory table > starts with the compilation directory which can only be gotten from > the CU (DW_AT_comp_dir). The files in the file list (which don't have > an explicit dir associated) are all given relative to that comp dir. you could take this information from the include directories: "11. include_directories (sequence of path names) Entries in this sequence describe each path that was searched for included = source files in this compilation. (The paths include those directories spec= ified explicitly by the user for the compiler to search and those the compi= ler searches without explicit direction.) Each path entry is either a full = path name or is relative to the current directory of the compilation. The last entry is followed by a single null byte. The line number program assigns numbers to each of the file entries in orde= r, beginning with 1. The current directory of the compilation is understood= to be the zeroth entry and is not explicitly represented." Kind Regards, Torsten