[SATYR PATCH] Always build GDB-output-based unwinder

Martin Milata mmilata at redhat.com
Thu Jul 25 14:56:07 UTC 2013


Previously it was built only when a native unwinding library was
present, which does not make any sense.

Signed-off-by: Martin Milata <mmilata at redhat.com>
---
 lib/core_unwind.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/lib/core_unwind.c b/lib/core_unwind.c
index f15a0f9..f8ec516 100644
--- a/lib/core_unwind.c
+++ b/lib/core_unwind.c
@@ -49,7 +49,7 @@ sr_parse_coredump(const char *coredump_filename,
     return NULL;
 }
 
-#else /* !defined WITH_LIBDWFL && !defined WITH_LIBUNWIND */
+#endif /* !defined WITH_LIBDWFL && !defined WITH_LIBUNWIND */
 
 /* FIXME: is there another way to pass the executable name to the find_elf
  * callback? */
@@ -444,5 +444,3 @@ sr_core_stacktrace_from_gdb(const char *gdb_output, const char *core_file,
     sr_gdb_stacktrace_free(gdb_stacktrace);
     return core_stacktrace;
 }
-
-#endif /* !defined WITH_LIBDWFL && !defined WITH_LIBUNWIND */
-- 
1.8.3.1



More information about the Crash-catcher mailing list