On Thu, Jun 19, 2014 at 3:46 PM, H. Peter Anvin wrote:
> On 06/18/2014 03:59 PM, Andy Lutomirski wrote:
>>
>> This may break make vdso_install with binutils before 2.17.50.0.17.
>> On the other hand, make vdso_install was probably never useful with
>> earlier binutils, since the installed files
On 06/18/2014 03:59 PM, Andy Lutomirski wrote:
>
> This may break make vdso_install with binutils before 2.17.50.0.17.
> On the other hand, make vdso_install was probably never useful with
> earlier binutils, since the installed files are AFAIK completely
> useless without build-id.
>
How does
On 06/18/2014 03:59 PM, Andy Lutomirski wrote:
This may break make vdso_install with binutils before 2.17.50.0.17.
On the other hand, make vdso_install was probably never useful with
earlier binutils, since the installed files are AFAIK completely
useless without build-id.
How does it
On Thu, Jun 19, 2014 at 3:46 PM, H. Peter Anvin h...@zytor.com wrote:
On 06/18/2014 03:59 PM, Andy Lutomirski wrote:
This may break make vdso_install with binutils before 2.17.50.0.17.
On the other hand, make vdso_install was probably never useful with
earlier binutils, since the installed
With this change, doing 'make vdso_install' and telling gdb:
set debug-file-directory /lib/modules/KVER/vdso
will enable vdso debugging with symbols. This is useful for
testing, but kernel RPM builds will probably want to manually delete
these symlinks or otherwise do something sensible when
With this change, doing 'make vdso_install' and telling gdb:
set debug-file-directory /lib/modules/KVER/vdso
will enable vdso debugging with symbols. This is useful for
testing, but kernel RPM builds will probably want to manually delete
these symlinks or otherwise do something sensible when
6 matches
Mail list logo
