Hi Mark,
> Am 26.03.2018 um 21:12 schrieb Mark Wielaard :
>
> Hi Sasha,
>
> On Mon, Mar 26, 2018 at 04:41:06PM +, Sasha Da Rocha Pinheiro wrote:
>> is it possible to read contents of .debug_line section without the
>> presence of a .debug_info section?
>
> No, because .debug_line sections n
Hi Sasha,
On Mon, Mar 26, 2018 at 04:45:13PM +, Sasha Da Rocha Pinheiro wrote:
> I have noticed that when we compile out-of-source, the paths returned
> from libdw are gonna be relative. Otherwise, they show up as full path.
> Have you noticed it?
This might be related to your last question.
Hi Sasha,
On Mon, Mar 26, 2018 at 04:41:06PM +, Sasha Da Rocha Pinheiro wrote:
> is it possible to read contents of .debug_line section without the
> presence of a .debug_info section?
No, because .debug_line sections need some information from the CU
which comes from the .debug_info. In part
Hi Sasha,
> Am 26.03.2018 um 18:45 schrieb Sasha Da Rocha Pinheiro
> :
>
> Hi,
>
> I have noticed that when we compile out-of-source, the paths returned from
> libdw are gonna be relative. Otherwise, they show up as full path.
> Have you noticed it?
>
> Regards,
> Sasha
this is the issue tha
On Montag, 26. März 2018 18:45:13 CEST Sasha Da Rocha Pinheiro wrote:
> Hi,
>
> I have noticed that when we compile out-of-source, the paths returned from
> libdw are gonna be relative. Otherwise, they show up as full path. Have you
> noticed it?
You are talking about source file paths, right? Fr
Hi,
I have noticed that when we compile out-of-source, the paths returned from
libdw are gonna be relative. Otherwise, they show up as full path.
Have you noticed it?
Regards,
Sasha
Hi,
is it possible to read contents of .debug_line section without the presence of
a .debug_info section?
We have CUDA binaries being generated with only .debug_line, and we wish to use
that. Is it possible to do that with libdw?
If not, any ideas of how to construct a minimum .debug_info in o
https://sourceware.org/bugzilla/show_bug.cgi?id=22976
--- Comment #3 from Mark Wielaard ---
I noticed there is a CVE linked to this bug report:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8769
Note that this bug was NOT in a released version of elfutils.
It was introduced by the impor