Some test binaries were missing and showed up in "git status".
Signed-off-by: Ulf Hermann
---
.gitignore | 12
1 file changed, 12 insertions(+)
diff --git a/.gitignore b/.gitignore
index c583347..0ee3af7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -93,6 +93,7 @@ Makefile.in
/test
When unwinding by frame pointer the unwinder might ask for invalid
addresses. We don't have to fail the test in this case. In fact
any broken dwarf information can lead to requests for invalid
addresses, also without frame pointer unwinding.
Signed-off-by: Ulf Hermann
---
tests/ChangeLog
This is useful to test unwinding without debug information. The
binaries being examined might still have frame pointers that allow
us to bridge the unknown symbols.
Signed-off-by: Ulf Hermann
---
tests/ChangeLog | 6 ++
tests/backtrace-subr.sh | 14 ++
tests/backtrace.c
Hi,
I have another patch here, that introduces the actual feature; a fallback mode
for unwinding by frame pointer if unwinding by cfi fails. Unfortunately your
mail server thinks it's spam, presumably because of the inline test binaries.
What can I do about that?
br,
Ulf Hermann
On Fri, 2017-02-10 at 15:25 +0100, Ulf Hermann wrote:
> I have another patch here, that introduces the actual feature; a
> fallback mode for unwinding by frame pointer if unwinding by cfi
> fails.
That sounds like a useful feature!
> Unfortunately your mail server thinks it's spam, presumably bec
Unfortunately your mail server thinks it's spam, presumably because of
the inline test binaries. What can I do about that?
Do you have the bounce message, then we can investigate.
Otherwise could you post the patch without the test binaries?
Then we get them some other way.
The bounce message
Try sending suspicious content via something like fpaste.org.
I don't think it's very suspicious, but I don't intend to start a pointless
argument as first thing I do here ;)
fpaste.org won't accept it either, but paste.kde.org does. So, here we go:
https://paste.kde.org/pgs6oqk2z
br,
Ulf
