commit 7d4a7d8c5861e6587176052ea71c30ab12a49084

Author: Vicențiu Ciorbaru <vicentiu@mariadb.org>

Date:   Mon May 30 22:33:34 2016 +0300

    [MDEV-9127] Crash reporter often fails to show the query that crashed

    Addreses are not necessarily between heap_start && heap_end. Malloc

    calls using mmap can place pointers outside these bounds. In this case,

    we'll warn the user that the query pointer is potentially invalid.

    However, we'll attempt to print the data anyway after we're done

    printing everything else.

diff --git a/sql/signal_handler.cc b/sql/signal_handler.cc

index 9dd3e53..f72eb67 100644

--- a/sql/signal_handler.cc

+++ b/sql/signal_handler.cc

@@ -64,13 +64,13 @@ extern "C" sig_handler handle_fatal_signal(int sig)

   struct tm tm;

 #ifdef HAVE_STACKTRACE

   THD *thd;

-#endif

   /*

      This flag remembers if the query pointer was found invalid.

      We will try and print the query at the end of the signal handler, in case

      we're wrong.

   */

   bool print_invalid_query_pointer= false;

+#endif

   if (segfaulted)

   {

@@ -276,6 +276,7 @@ extern "C" sig_handler handle_fatal_signal(int sig)

       "\"mlockall\" bugs.\n");

   }

+#ifdef HAVE_STACKTRACE

   if (print_invalid_query_pointer)

   {

     my_safe_printf_stderr(

@@ -285,6 +286,7 @@ extern "C" sig_handler handle_fatal_signal(int sig)

     my_write_stderr(thd->query(), MY_MIN(65536U, thd->query_length()));

     my_safe_printf_stderr("\n\n");

   }

+#endif

 #ifdef HAVE_WRITE_CORE

   if (test_flags & TEST_CORE_ON_SIGNAL)