summaryrefslogtreecommitdiff
path: root/include/my_stacktrace.h
diff options
context:
space:
mode:
authorVicențiu Ciorbaru <vicentiu@mariadb.org>2016-05-30 22:33:34 +0300
committerVicențiu Ciorbaru <vicentiu@mariadb.org>2016-07-12 11:58:20 +0300
commit7d4a7d8c5861e6587176052ea71c30ab12a49084 (patch)
tree80e3c545b5067c01215bbee589404af99961069e /include/my_stacktrace.h
parent406fe77763c43dd7e151d92364e0296539077d4a (diff)
downloadmariadb-git-7d4a7d8c5861e6587176052ea71c30ab12a49084.tar.gz
[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.
Diffstat (limited to 'include/my_stacktrace.h')
-rw-r--r--include/my_stacktrace.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/my_stacktrace.h b/include/my_stacktrace.h
index fb2525e3a12..fad6e532de9 100644
--- a/include/my_stacktrace.h
+++ b/include/my_stacktrace.h
@@ -45,7 +45,7 @@ C_MODE_START
#if defined(HAVE_STACKTRACE) || defined(HAVE_BACKTRACE)
void my_init_stacktrace();
void my_print_stacktrace(uchar* stack_bottom, ulong thread_stack);
-void my_safe_print_str(const char* val, int max_len);
+int my_safe_print_str(const char* val, int max_len);
void my_write_core(int sig);
#if BACKTRACE_DEMANGLE
char *my_demangle(const char *mangled_name, int *status);