Hello everyone,
please forgive my rather noob-ish question but I'm very confused on how libelf
works.
My end goal is to add a DT_NEEDED entry into an arbitrary elf file, but before
this I should just print the DT_NEEDED entries like this:
```C
// Some code that copies a source_elf_file to a
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #16 from Frank Ch. Eigler ---
(yup, misinterpreted what the "this" was you meant, sorry!)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #15 from Eli Schwartz ---
Wouldn't that be covered by "libdebuginfod disabled equals dummy enabled"?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #14 from Frank Ch. Eigler ---
It's not just for testing purposes. It's to aid bootstrapping new OS versions,
by reducing the transitive requirements of elfutils in the buildroot.
--
You are receiving this mail because:
You are o
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #13 from Eli Schwartz ---
I think we'd prefer to have the ability to build libdebuginfod without the
server. Ambivalent about a special option to force the libdebuginfod dummy to
be created, but...
If it's just for testing purpose
Hi David,
On Fri, 2020-06-19 at 17:46 -0700, David Blaikie via Elfutils-devel wrote:
> On Fri, Jun 19, 2020 at 5:00 AM Mark Wielaard wrote:
> > I think that is kind of the point of Early Debug. Only use DWARF (at
> > first) for address/range-less data like types and program scope
> > entries, but
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #12 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #11)
> Martin, could you comment on the setup? Does this help your case? I will
> probably not actually use it myself, so don't want to add it unless it
> really ma
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #11 from Mark Wielaard ---
(In reply to Frank Ch. Eigler from comment #10)
> Comment on attachment 12628 [details]
> debuginfod: Add --disable-libdebuginfod and --enable-libdebuginfod=dummy.
>
> Looks workable.
>
> I don't know i
Hi,
On Wed, 2020-06-17 at 00:25 +0200, Mark Wielaard wrote:
> Although we check for and/or create the interval_path right before,
> there is still a possibility that the fopen call fails. Handle that
> as if the file is unreadable.
On Wed, 2020-06-17 at 00:25 +0200, Mark Wielaard wrote:
> We need
Hello Mark,
thanks a billion for you answer! You gave me a very good starting point!
Kindly,
Anastasios
> On 19 Jun 2020, at 21:15, Mark Wielaard wrote:
>
> Hi,
>
> On Thu, 2020-06-11 at 15:25 +0100, Anastasios Andronidis via Elfutils-
> devel wrote:
>> Could someone please help me with this
https://sourceware.org/bugzilla/show_bug.cgi?id=26043
--- Comment #7 from devel.origin at gmail dot com ---
For that demo the debug files are ending up in a custom directory (the
build-id-demo/.build-id/) for the packge builder to pick up. So they can't be
found by GDB. When packages are installed
11 matches
Mail list logo
