fprintf() and exit() do the same job and are portable.
(v1 was missing the errno.h include in allfcts.c)
Signed-off-by: Ulf Hermann
---
tests/ChangeLog | 6 ++
tests/allfcts.c | 47 ---
tests/buildid.c | 6 +++---
tests/debugaltli
Hi Mark,
> Thanks a lot for all your work and posting the patches.
> I will go through them next week.
Thanks for reviewing them. The ones that got accepted will already make my life
easier.
> I quickly scanned some just now. Some seem fine to go in. But others are
> a bit more iffy. I think so
On windows x86_64 pid_t is 64bit wide. We need to adapt our printf
format respectively.
(We can actually print the extra bits in a portable way, so let's do it
rather than casting to int and ignoring them.)
Signed-off-by: Ulf Hermann
---
src/ChangeLog | 4
src/stack.c | 22 ++
We assume core files from linux systems, so we should use the linux
version of the signals when reading them. Other OS might have different
signal numbers.
Signed-off-by: Ulf Hermann
---
src/readelf.c | 25 -
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a
Hi Adam,
On Fri, 2017-05-05 at 18:25 +0200, Adam Šulc wrote:
> I work on ABRT improvement in order to increase security related to
> core backtrace generating using elfutils library.
> Here is a short description of my problem:
>
> Goal is to not call base code in elfutils and gdb functions under
On Sat, 2017-05-06 at 13:30 +0200, Milian Wolff wrote:
> On Freitag, 5. Mai 2017 15:06:48 CEST Mark Wielaard wrote:
> > On Thu, 2017-05-04 at 18:05 +0200, Milian Wolff wrote:
> > > I noticed that elfutils fails to handle clang binaries when we want to
> > > find a DIE for a certain address. I.e. dw
Hi,
I frequently get failures from the run-dwarf-getmacros.sh test, on
testfile-macros:0xb. The test repeatedly outputs "(null)" instead of the
actual macros and then runs into the assert at dwarf-getmacros.c:50. The
failure is very nondeterministic, though. I haven't found a reliable way
to
