[PATCH 1/4] configure.ac: Add -fasynchronous-unwind-tables to CROSSLDFLAGS.

[Rémi Bernon]

When available. Otherwise the output_cfi calls in winebuild, in the
syscall thunks for instance, are just no-op.

Signed-off-by: Rémi Bernon <rbernon at codeweavers.com>
---

This series makes it possible for Gdb to unwind the stack through the
syscall dispatcher. I'm not completely sure it's right, and more
precisely I don't know if PATCH 4 is okay, and if the kernel stack must
be above the user stack.

Sadly, other tools such as perf or valgrind still struggle with what
they consider a huge stack frame between the kernel stack and the user
stack when NT syscalls are executed. I'm not completely sure how this
could be mitigated.

 configure.ac | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configure.ac b/configure.ac
index c0a126293c4..fb5447addd4 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2105,6 +2105,7 @@ then
    DLLFLAGS="$DLLFLAGS -fasynchronous-unwind-tables"
    LDDLLFLAGS="$LDDLLFLAGS -fasynchronous-unwind-tables"
    UNIXDLLFLAGS="$UNIXDLLFLAGS -fasynchronous-unwind-tables"
+   CROSSLDFLAGS="$CROSSLDFLAGS -fasynchronous-unwind-tables"
 else
    if test "x$enable_win64" = "xyes"
    then
-- 
2.33.0