Re: What not as assembler and it's debugger?

2019-10-04 Thread Mark Wielaard 
On Sun, Sep 15, 2019 at 09:14:01AM +0530, Mayuresh Kathe wrote:
> Since the elfutils project provides a Linux-only tuned edition of ELF binary
> management toolkit, why does it not also include an assembler and it's
> associated debugger?
> 
> I understand that the AT&T mnemonics are something of a standard under Unix
> and Unix-like operating systems, and that GNU binutils provides "as" for the
> same, but since elfutils provides replacements for almost all of the
> utilities from binutils why not an assembler too?

The simple answer is, not enough time.
There is a start of an assembler/disassembler in elfutils/libasm.
But the number of architectures it supports is currently very limited.

Likewise for a full debugger. There is some support for debugger like
functionality in the DWARF Frontend Library (libdwfl). But extending
that to a traditional debugger is a lot of work. Although people have
done something like that, see https://sourceware.org/systemtap and
https://drgn.readthedocs.io.

Cheers,

Mark

[Bug general/24498] 0.176: isn't LTO ready

2019-10-04 Thread mark at klomp dot org 
https://sourceware.org/bugzilla/show_bug.cgi?id=24498

Mark Wielaard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2019-10-04
 Ever confirmed|0   |1

--- Comment #5 from Mark Wielaard  ---
This is still the same GCC issue:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200

Once gcc gets support for symbol versioning usable with LTO we'll use it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: [PATCH] elflint, readelf: enhance error diagnostics

2019-10-04 Thread Mark Wielaard 
On Mon, Sep 30, 2019 at 02:39:50PM +0300, Dmitry V. Levin wrote:
> When an input file cannot be opened, include its name
> into the error diagnostics.

Looks very sensible. Pushed to master.

Thanks,

Mark