ELF Dissector in kdereview

[Volker Krause]

I haven't recently tested it on 32bit ARM, I pushed a possible fix using a 
similar approach that has been applied for x86 already. If that doesn't help I 
need to find a 32bit ARM setup again here to properly debug it.

Regards,
Volker

On Tuesday, 29 October 2019 11:29:44 CET Jonathan Riddell wrote:
> I'm getting a build failure for this on 32-bit arm
> 
> https://build.neon.kde.org/job/bionic_unstable_neon-packaging_elf-dissector_
> bin_armhf/7/console
> 
> disassembler.cpp:149:34: error: ‘print_insn_little_arm’ was not
> declared in this scope
> 
> Is it expected to build on this architecture?  It builds fine on 64 bit arm.
> 
> 
> Jonathan
> 
> On Sun, 27 Oct 2019 at 09:27, Volker Krause <vkrause at kde.org> wrote:
> > Thanks again for the feedback, this has now been moved to extragear/sdk.
> > 
> > On Saturday, 28 September 2019 13:01:11 CET Volker Krause wrote:
> > > Hi,
> > > 
> > > ELF Dissector has been moved to kdereview for the usual review process.
> > > 
> > > https://phabricator.kde.org/source/elf-dissector/
> > > 
> > > ELF Dissector is a static analysis tool for ELF libraries and
> > 
> > executables,
> > 
> > > for doing things like inspecting forward and backward dependencies (on a
> > > library or symbol level), identifying load-time performance bottlenecks
> > > such as expensive static constructors or excessive relocations, or size
> > > profiling of ELF files.
> > > 
> > > ELF Dissector has been living in playground for more than 6 years
> > 
> > because I
> > 
> > > was sloppy following the right process. Since it's in active use by a
> > 
> > number
> > 
> > > of people, is actively maintained and remains relevant and useful I
> > > think
> > > it's time to finally rectify this :)
> > > 
> > > Regarding its final destination, extragear/sdk looks like the obvious
> > > candidate, as its such a niche tool that being part of the KDE
> > 
> > Application
> > 
> > > bundle is probably hard to argue. Once KDE Applications and the "release
> > > service" are sufficiently decoupled, I'd of course be more than happy to
> > > have it covered by the automatic release process.
> > > 
> > > Regarding distribution, there is one annoying aspect, its dependency on
> > > semi- public binutils API for accessing the C++ symbol demangling AST.
> > 
> > That
> > 
> > > works on conventional Linux distributions, but I failed to make it work
> > 
> > as
> > 
> > > a Flatpak due to that.
> > > 
> > > Regarding portability, this currently only builds on ELF-based systems,
> > > although theoretically this could be useful on a Windows host used for
> > > embedded Linux development too. It's not impossible to make this work
> > > eventually I think, but it's probably quite some work.
> > > 
> > > Thanks,
> > > Volker

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20191029/01ad6d85/attachment.sig>