Hi Mark,
I am mainly wondering why binutils strip already seems to keep ".ctf"
sections (even without -g).
Right. But I am wondering how that mechanism works with binutils strip.
Apparently we do something different in eu-strip which makes it
necessary to add a --keep-ctf option based on the
Hi Mark,
O, this surprises me. I wasn't aware binutils strip keeps unallocated
sections by default. But apparently it does. It doesn't seem specific
to ".ctf". Do you know why? This seems counter to how strip is supposed
to behave, at least how I understand it.
Actually thinking about it, ther
Hi Mark,
Oh, I see, thanks for your comment!. My intention with this patch is to
replicate the same proceeding by _default_ implemented in `binutils strip'
tool, it is: not remove CTF section, except it is indicated explicitly.
O, this surprises me. I wasn't aware binutils strip keeps unalloca
Hi Guys,
I apologise - I know that Jose CC'ed me on this topic, but I have lost
the email, so I am creating this post instead.
What about using an OS-specific section flag in elf.h, something like:
#define SHF_GNU_PERSISTENT 0x0ff1 /* Section must not be stripped. */
I rather like
Hi Mark,
$ git clone git://sourceware.org/git/dwz.git
$ cd dwz
$ ./configure
$ make
$ cp dwz one
$ cp dwz two
$ dwz --dwarf-5 -m sup one two
Thanks. Using those files as a guide I have added some initial support for
displaying and following .debug_sup sections to readelf and objdump.
Cheers
Hi Mark,
Context is that dwz 0.15 (still not released yet) can now produce
standardized DWARF Supplementary Files using a .debug_sup section
when using --dwarf-5 -m multifile. See this bug report:
https://sourceware.org/bugzilla/show_bug.cgi?id=27440
Is there somewhere that I can lay my hands
Hi Guys,
I have now applied the attached patch to the binutils sources to fix the
problem there.
Cheers
Nick
diff --git a/bfd/bfd.c b/bfd/bfd.c
index ec38a0673c..449bcc6cef 100644
--- a/bfd/bfd.c
+++ b/bfd/bfd.c
@@ -2558,6 +2558,7 @@ bfd_update_compression_header (bfd *abfd, bfd_byte *conte