[bug #48463] segmentation fault

[tsimd]

URL:
  <http://savannah.gnu.org/bugs/?48463>

                 Summary: segmentation fault
                 Project: texinfo - GNU documentation system
            Submitted by: tsimd
            Submitted on: Mon 11 Jul 2016 11:11:37 AM GMT
                Category: info
                 Release: 6.1dev
                Priority: 7 - High
                Severity: 3 - Normal
              Item Group: bug
                 Privacy: Public
             Open/Closed: Open
             Assigned to: None
         Discussion Lock: Any
                  Status: None

    _______________________________________________________

Details:

I get a segmentation fault when I enter the following commands. I start info
with `info gettext`, then M-x index-apropos and type gettext. It happens with
other info files as well. 

valgrind output: ==16388== Memcheck, a memory error detector
==16388== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==16388== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==16388== Command: info/ginfo gettext
==16388== Parent PID: 2801
==16388== 
==16388== Invalid read of size 1
==16388==    at 0x42AB27: mbiter_multi_next (mbiter.h:131)
==16388==    by 0x4045E6: display_update_node_text (display.c:540)
==16388==    by 0x404B1B: display_update_one_window (display.c:701)
==16388==    by 0x403496: display_update_display (display.c:87)
==16388==    by 0x41ABAE: info_read_and_dispatch (session.c:238)
==16388==    by 0x41AB82: info_session (session.c:221)
==16388==    by 0x410821: main (info.c:1039)
==16388==  Address 0x98f3bed is not stack'd, malloc'd or (recently) free'd
==16388== 
==16388== 
==16388== Process terminating with default action of signal 11 (SIGSEGV)
==16388==  Access not within mapped region at address 0x98F3BED
==16388==    at 0x42AB27: mbiter_multi_next (mbiter.h:131)
==16388==    by 0x4045E6: display_update_node_text (display.c:540)
==16388==    by 0x404B1B: display_update_one_window (display.c:701)
==16388==    by 0x403496: display_update_display (display.c:87)
==16388==    by 0x41ABAE: info_read_and_dispatch (session.c:238)
==16388==    by 0x41AB82: info_session (session.c:221)
==16388==    by 0x410821: main (info.c:1039)
==16388==  If you believe this happened as a result of a stack
==16388==  overflow in your program's main thread (unlikely but
==16388==  possible), you can try to increase the size of the
==16388==  main thread stack using the --main-stacksize= flag.
==16388==  The main thread stack size used in this run was 8388608.
==16388== 
==16388== HEAP SUMMARY:
==16388==     in use at exit: 11,568,013 bytes in 183,469 blocks
==16388==   total heap usage: 535,450 allocs, 351,981 frees, 11,049,397,779
bytes allocated
==16388== 
==16388== LEAK SUMMARY:
==16388==    definitely lost: 0 bytes in 0 blocks
==16388==    indirectly lost: 0 bytes in 0 blocks
==16388==      possibly lost: 0 bytes in 0 blocks
==16388==    still reachable: 11,568,013 bytes in 183,469 blocks
==16388==         suppressed: 0 bytes in 0 blocks
==16388== Reachable blocks (those to which a pointer was found) are not
shown.
==16388== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==16388== 
==16388== For counts of detected and suppressed errors, rerun with: -v
==16388== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48463>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/