On Tue, 2017-02-14 at 21:58 -0500, Mike Frysinger wrote:
> On 09 Feb 2017 21:13, Mark Wielaard wrote:
> > +# See if we can add -D_FORTIFY_SOURCE=2. Don't do it if it is already
> > +# (differently) defined or if it generates warnings/errors because we
> > +# don't use the right optimisation level (
ppc64 and ppc64le ELF files can also contain a power specific
.gnu.attributes section. Add support for those and recognize the new
GNU_Power_ABI_FP Single-precision hard float value.
Signed-off-by: Mark Wielaard
---
backends/ChangeLog | 6 ++
backends/ppc64_init.c |
This makes it easier to write a replacement for it on systems where
sysconf(3) doesn't exist.
---
lib/ChangeLog | 4
lib/crc32_file.c | 2 +-
libdwfl/ChangeLog | 5 +
libdwfl/linux-kernel-modules.c | 2 +-
libdwfl/linux-proc-maps.c | 2 +-
This makes it easier to write a replacement for it on systems where
sysconf(3) doesn't exist.
Signed-off-by: Ulf Hermann
---
lib/ChangeLog | 4
lib/crc32_file.c | 2 +-
libdwfl/ChangeLog | 5 +
libdwfl/linux-kernel-modules.c | 2 +-
libdwfl/l
On Tue, 2017-02-14 at 14:30 +0100, Ulf Hermann wrote:
> We only need it in nm.c and objdump.c, but it pulls in argp as
> dependency. By dropping it from libeu.h, the libraries can be
> compiled without argp.
Looks fine. Applied.
Note that elfutils configure already checks for a separate argp libr
On Wed, 2017-02-15 at 15:28 +0100, Ulf Hermann wrote:
> This makes it easier to write a replacement for it on systems where
> sysconf(3) doesn't exist.
To be honest I don't know if it makes sense to port elfutils to a
platform where sysconf doesn't even exist. But the patch is OK. The
correct spel
Hi,
I put all three frame pointer unwinding fallback patches on
the mjw/fp-unwind branch. I'll also sent them to the list using
git send-mail --annotate taking out the binary file patches.
Hopefully that will make them appear on the list, bypassing the
spam filters.
[PATCH 1/3] Add frame pointer
From: Ulf Hermann
If we don't find any debug information for a given frame, we usually
cannot unwind any further. However, the binary in question might have
been compiled with frame pointers, in which case we can look up the
well known frame pointer locations in the stack snapshot and use them
to
From: Ulf Hermann
If we don't find any debug information for a given frame, we usually
cannot unwind any further. However, the binary in question might have
been compiled with frame pointers, in which case we can look up the
well known frame pointer locations in the stack snapshot and use them
to
From: Ulf Hermann
If we don't find any debug information for a given frame, we usually
cannot unwind any further. However, the binary in question might have
been compiled with frame pointers, in which case we can look up the
well known frame pointer locations in the stack snapshot and use them
to
10 matches
Mail list logo