Re: [PATCH 1/2] libelf: Sync elf.h from glibc.
On Sat, 2020-08-29 at 00:42 +0200, Mark Wielaard wrote: > Gets us DT_AARCH64_BTI_PLT and DT_AARCH64_PAC_PLT. Pushed.
Re: [PATCH 2/2] backends: Implement aarch64_dynamic_tag_name and aarch64_dynamic_tag_check
On Sat, 2020-08-29 at 00:42 +0200, Mark Wielaard wrote: > +2020-08-28 Mark Wielard > + > + * aarch64_init.c (aarch64_init): Hook dynamic_tag_name and > + dynamic_tag_check. > + * aarch64_symbol.c (aarch64_dynamic_tag_name): New function. > + (aarch64_dynamic_tag_check): Likewise. Pushed.
Re: [PATCH] readelf: base address entry can be first
On Tue, 2020-09-01 at 23:48 +0200, Mark Wielaard wrote: > In both debug_ranges and debug_loc a base address entry can be the > first in the range or loc list. If so print the offset and set first > to false. Otherwise don't print the entry list offset, but do set > first to false. Pushed.
Re: [PATCH] libebl: Handle aarch64 bti, pac bits in gnu property note
On Thu, 2020-09-03 at 17:28 +0200, Mark Wielaard wrote: > On Thu, 2020-09-03 at 11:56 +0200, Mark Wielaard wrote: > > When building with gcc -mbranch-protection= we might get a gnu property > > note indicating BTI (Branch Target Identification) and/or PAC (Pointer > > Authentication Code) is being used. > > > > Add a small testcase to show eu-readelf -n now properly lists those > > bits in the gnu property note. > > Oops. Forgot to add the new testfile to EXTRA_DIST. > > diff --git a/tests/ChangeLog b/tests/ChangeLog > index cb2e9956..61c6cb7c 100644 > --- a/tests/ChangeLog > +++ b/tests/ChangeLog > @@ -2,6 +2,8 @@ > > * testfile-gnu-property-note-aarch64.bz2: New file. > * run-readelf-n.sh: Handle testfile-gnu-property-note-aarch64. > + * Makefile.am (EXTRA_DIST): Add > + testfile-gnu-property-note-aarch64.bz2. Pushed with this addition.
Re: [PATCH] libdw,readelf: Recognize DW_CFA_AARCH64_negate_ra_state
On Thu, 2020-09-03 at 17:58 +0200, Mark Wielaard wrote: > DW_CFA_AARCH64_negate_ra_state is used on aarch64 to indicate whether > or not the return address is mangled or not. This has the same value > as the DW_CFA_GNU_window_save. So we have to pass around the e_machine > value of the process or core we are inspecting to know which one to > use. > > Note that it isn't actually implemented yet. It needs ARMv8.3 hardware. > If we don't have such hardware it is enough to simply ignore the > DW_CFA_AARCH64_negate_ra_state (and not confuse it with > DW_CFA_GNU_window_save) to get backtraces to work on aarch64. > > Add a testcase for eu-readelf --debug-dump=frames to show the value > is correctly recognized. Also don't warn we cannot find any DWARF > if we are just dumping frames (those will come from .eh_frame if > there is no .debug_frame). Pushed.
Re: Doing a 0.181 release (arm64 bti/pac issues)
Hi, On Wed, 2020-09-02 at 15:03 +0200, Mark Wielaard wrote: > On irc Martin was asking about doing a new release. I do think it is > time for 0.181. But I am struggling a bit with Fedora arm64 which has > turned on BTI/PAC which caused some issues: > https://bugzilla.redhat.com/show_bug.cgi?id=1861423 > > I have patches for the dynamic tag parsing already posted to the list > and working on the new property notes. But I don't fully understand > why backtracing is broken right now. > > I would like to resolve those issues before doing a release (hopefully > later this or next week). The arm64 bti/pac issues are resolved (although we can still not unwind when PAC is active, but that needs newer hardware than anybody has at the moment). I believe all patches are in git now. And I like to do a 0.181 release tomorrow unless there are still pending issues/patches. Cheers, Mark
[Bug tools/23787] eu-size: Bad handling of ar files inside are files
https://sourceware.org/bugzilla/show_bug.cgi?id=23787 Ikechukwu ike changed: What|Removed |Added CC||support at youwin dot org.ng --- Comment #33 from Ikechukwu ike --- https://techdownloadforpc.com/westinghouse-smart-landscape-app-pc-windows-7810-mac-free-download/ -- You are receiving this mail because: You are on the CC list for the bug.
