Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-12635

innodb.log_file_size fails when run with Valgrind

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/10024/steps/test/logs/stdio

      innodb.log_file_size 'innodb_plugin'     w1 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-04-27 12:46:33
      line
      ==32675== Thread 7:
      ==32675== Jump to the invalid address stated on the next line
      ==32675==    at 0xC0816E2: ???
      ==32675==    by 0xC081AB1: ???
      ==32675==    by 0xBF9480A: ???
      ==32675==    by 0xC1655C3: ???
      ==32675==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==32675==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==32675==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==32675== Process terminating with default action of signal 11 (SIGSEGV): dumping core
      ==32675==  Access not within mapped region at address 0xC0816E2
      ==32675==    at 0xC0816E2: ???
      ==32675==    by 0xC081AB1: ???
      ==32675==    by 0xBF9480A: ???
      ==32675==    by 0xC1655C3: ???
      ==32675==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==32675==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==32675==  If you believe this happened as a result of a stack
      ==32675==  overflow in your program's main thread (unlikely but
      ==32675==  possible), you can try to increase the size of the
      ==32675==  main thread stack using the --main-stacksize= flag.
      ==32675==  The main thread stack size used in this run was 8388608.
      ==300== Thread 7:
      ==300== Jump to the invalid address stated on the next line
      ==300==    at 0xC0816E2: ???
      ==300==    by 0xC081AB1: ???
      ==300==    by 0xBF9480A: ???
      ==300==    by 0xC1655C3: ???
      ==300==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==300==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==300==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==300== Invalid read of size 1
      ==300==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==300==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==300==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==300==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==300==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==300==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==300==    by 0xC0816E1: ???
      ==300==    by 0xC081AB1: ???
      ==300==    by 0xBF9480A: ???
      ==300==    by 0xC1655C3: ???
      ==300==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==300==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==300==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==300== Process terminating with default action of signal 11 (SIGSEGV): dumping core
      ==300==  Access not within mapped region at address 0xC0816E2
      ==300==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==300==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==300==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==300==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==300==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==300==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==300==    by 0xC0816E1: ???
      ==300==    by 0xC081AB1: ???
      ==300==    by 0xBF9480A: ???
      ==300==    by 0xC1655C3: ???
      ==300==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==300==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==300==  If you believe this happened as a result of a stack
      ==300==  overflow in your program's main thread (unlikely but
      ==300==  possible), you can try to increase the size of the
      ==300==  main thread stack using the --main-stacksize= flag.
      ==300==  The main thread stack size used in this run was 8388608.
      ==339== Thread 7:
      ==339== Jump to the invalid address stated on the next line
      ==339==    at 0xC0816E2: ???
      ==339==    by 0xC081AB1: ???
      ==339==    by 0xBF9480A: ???
      ==339==    by 0xC1655C3: ???
      ==339==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==339==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==339==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==339== Invalid read of size 1
      ==339==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==339==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==339==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==339==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==339==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==339==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==339==    by 0xC0816E1: ???
      ==339==    by 0xC081AB1: ???
      ==339==    by 0xBF9480A: ???
      ==339==    by 0xC1655C3: ???
      ==339==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==339==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==339==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==339== Process terminating with default action of signal 11 (SIGSEGV): dumping core
      ==339==  Access not within mapped region at address 0xC0816E2
      ==339==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==339==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==339==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==339==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==339==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==339==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==339==    by 0xC0816E1: ???
      ==339==    by 0xC081AB1: ???
      ==339==    by 0xBF9480A: ???
      ==339==    by 0xC1655C3: ???
      ==339==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==339==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==339==  If you believe this happened as a result of a stack
      ==339==  overflow in your program's main thread (unlikely but
      ==339==  possible), you can try to increase the size of the
      ==339==  main thread stack using the --main-stacksize= flag.
      ==339==  The main thread stack size used in this run was 8388608.
      ==359== Thread 9:
      ==359== Jump to the invalid address stated on the next line
      ==359==    at 0xC0816E2: ???
      ==359==    by 0xC081AB1: ???
      ==359==    by 0xBF9480A: ???
      ==359==    by 0xC1655C3: ???
      ==359==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==359==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==359==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==359== Invalid read of size 1
      ==359==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==359==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==359==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==359==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==359==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==359==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==359==    by 0xC0816E1: ???
      ==359==    by 0xC081AB1: ???
      ==359==    by 0xBF9480A: ???
      ==359==    by 0xC1655C3: ???
      ==359==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==359==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==359==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==359== Process terminating with default action of signal 11 (SIGSEGV): dumping core
      ==359==  Access not within mapped region at address 0xC0816E2
      ==359==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==359==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==359==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==359==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==359==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==359==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==359==    by 0xC0816E1: ???
      ==359==    by 0xC081AB1: ???
      ==359==    by 0xBF9480A: ???
      ==359==    by 0xC1655C3: ???
      ==359==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==359==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==359==  If you believe this happened as a result of a stack
      ==359==  overflow in your program's main thread (unlikely but
      ==359==  possible), you can try to increase the size of the
      ==359==  main thread stack using the --main-stacksize= flag.
      ==359==  The main thread stack size used in this run was 8388608.
      ==494== Thread 4:
      ==494== Jump to the invalid address stated on the next line
      ==494==    at 0xC0816E2: ???
      ==494==    by 0xC081AB1: ???
      ==494==    by 0xBF9480A: ???
      ==494==    by 0xC1655C3: ???
      ==494==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==494==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==494==  Address 0xc0816e2 is not stack'dworker[1] > Restart  - not started
      , malloc'd or (recently) free'd
      ==494== Invalid read of size 1
      ==494==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==494==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==494==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==494==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==494==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==494==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==494==    by 0xC0816E1: ???
      ==494==    by 0xC081AB1: ???
      ==494==    by 0xBF9480A: ???
      ==494==    by 0xC1655C3: ???
      ==494==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==494==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==494==  Address 0xc0816e2 is not stack'd, malloc'd or (recently) free'd
      ==494== Process terminating with default action of signal 11 (SIGSEGV): dumping core
      ==494==  Access not within mapped region at address 0xC0816E2
      ==494==    at 0x683A4E8: ??? (in /lib64/libgcc_s.so.1)
      ==494==    by 0x683B3E8: _Unwind_Backtrace (in /lib64/libgcc_s.so.1)
      ==494==    by 0x6B36205: backtrace (in /lib64/libc-2.18.so)
      ==494==    by 0xF20D94: my_print_stacktrace (stacktrace.c:267)
      ==494==    by 0x868232: handle_fatal_signal (signal_handler.cc:166)
      ==494==    by 0x4E439EF: ??? (in /lib64/libpthread-2.18.so)
      ==494==    by 0xC0816E1: ???
      ==494==    by 0xC081AB1: ???
      ==494==    by 0xBF9480A: ???
      ==494==    by 0xC1655C3: ???
      ==494==    by 0x4E3C0DA: start_thread (in /lib64/libpthread-2.18.so)
      ==494==    by 0x6B28E3C: clone (in /lib64/libc-2.18.so)
      ==494==  If you believe this happened as a result of a stack
      ==494==  overflow in your program's main thread (unlikely but
      ==494==  possible), you can try to increase the size of the
      ==494==  main thread stack using the --main-stacksize= flag.
      ==494==  The main thread stack size used in this run was 8388608.
      

        Attachments

          Activity

            People

            • Assignee:
              marko Marko Mäkelä
              Reporter:
              elenst Elena Stepanova
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: