Do you have the whole call stack of that failed __libdw_read_offset
call? Which source line in tests/dwarf-getmacros.c prints the "(null)"?
Actually I just managed to catch a backtrace by inserting an infinite
loop at the point where it would normally return -1. It turns out the
address we are l
Do you have the whole call stack of that failed __libdw_read_offset
call? Which source line in tests/dwarf-getmacros.c prints the "(null)"?
Actually I just managed to catch a backtrace by inserting an infinite
loop at the point where it would normally return -1. It turns out the
address we are
> Is it only with testfile-macros?
> All other testfiles always run correctly?
Yes, it only happens with the testfile-macros check at 0xb.
> Do you have the whole call stack of that failed __libdw_read_offset
> call? Which source line in tests/dwarf-getmacros.c prints the "(null)"?
I'm having a
On Mon, 2017-05-08 at 18:22 +0200, Ulf Hermann wrote:
> 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 nonde
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
