From f1c375d0068eb79fd42024bf4e6f4216e13881cf Mon Sep 17 00:00:00 2001 From: Guy Harris Date: Mon, 11 May 2015 13:29:08 -0700 Subject: [PATCH] Try to handle the executable being a libtool wrapper. Change-Id: I8fd2b4445707029ea24ad3c02804c0bf8fcedd15 Reviewed-on: https://code.wireshark.org/review/8406 Reviewed-by: Guy Harris --- test/run_and_catch_crashes | 31 +++++++++++++++++++++++++++++-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git a/test/run_and_catch_crashes b/test/run_and_catch_crashes index 28411c2242..282d131df2 100755 --- a/test/run_and_catch_crashes +++ b/test/run_and_catch_crashes @@ -51,6 +51,17 @@ then then # # Found the executable. + # Is it a libtool wrapper script? Look for a .libs + # directory. + # + executable_dirname=`dirname "$executable"` + if [ -d "$executable_dirname"/.libs ] + then + is_libtool_wrapper=yes + else + is_libtool_wrapper=no + fi + # # Now, look for a debugger. # XXX - lldb? @@ -63,10 +74,18 @@ then # cause the stack trace to go to the standard # error. # - dbx "$executable" core 1>&2 <&2 <&2 <&2 <&2 <&2 <