Re: Segmentation fault while searching

[Gavin Smith]

On 9 December 2015 at 23:05, mtsio <address@hidden> wrote:
> Hello everyone,
>
> I was reading the gettext manual with 'info gettext' (info 6.0). To
> reproduce start searching something which isn't in the document with
> C-s. When you get 'Failing Regexp I-search:' at the bottom line hit C-g.
>

I couldn't reproduce this. The only error I managed to get under valgrind was

==2559== Conditional jump or move depends on uninitialised value(s)
==2559==    at 0x4169BDD: re_compile_fastmap_iter.isra.16 (in /lib/libc-2.17.so)
==2559==    by 0x4178875: re_compile_fastmap (in /lib/libc-2.17.so)
==2559==    by 0x4178E4F: regcomp (in /lib/libc-2.17.so)
==2559==    by 0x805CD3A: regexp_search (search.c:158)
==2559==    by 0x80632C8: info_search_in_node_internal (session.c:3999)
==2559==    by 0x80635E5: info_search_internal (session.c:4135)
==2559==    by 0x80651F5: incremental_search (session.c:5245)
==2559==    by 0x80645EC: isearch_forward (session.c:4799)
==2559==    by 0x805DCC4: info_read_and_dispatch (session.c:253)
==2559==    by 0x805DC20: info_session (session.c:221)
==2559==    by 0x8055894: main (info.c:1025)

But this was after adding a single letter to the search, not after
pressing C-g. It could either be a libc or valgrind bug
(https://bugzilla.redhat.com/show_bug.cgi?id=174324).

Does it just happen with that file (gettext) or others as well? Do you
know how to get a backtrace from the core file?