bug#40477: closed (Segfault with grep-3.4 and pcre-8.44)

[GNU bug Tracking System]

Your message dated Mon, 21 Sep 2020 12:19:57 -0700
with message-id <44ca5390-4a45-5aa2-249b-3ec10d2e24ad@cs.ucla.edu>
and subject line Re: bug#40477: Segfault with grep-3.4 and pcre-8.44
has caused the debbugs.gnu.org bug report #40477,
regarding Segfault with grep-3.4 and pcre-8.44
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
40477: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40477
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Segfault with grep-3.4 and pcre-8.44
>
>
>
>
> Date: 
>
> Mon, 6 Apr 2020 15:54:47 -0500
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
>
>
>
>
> In linuxfromscratch we normally build grep without pcre using:
>
> ./configure --prefix=/usr --bindir=/bin
> make
>
> It works fine.
>
> Later after pcre is installed users can rebuild grep with exactly the 
> same instructions, but with grep-3.4, I get a segfault with
>
> grep --help
>
> and all other command line entries.  Adding --disable-perl-regexp 
> restores grep but of course removes pcre regex capabilities.
>
> I went back and built grep-3.3 with pcre and everything worked with the 
> same pcre library as above.
>
> I did some preliminary gdb testing and got:
>
> Reading symbols from src/grep...
> (gdb) run --help
> Starting program: /build/grep/grep-3.4/src/grep --help
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000041cc03 in __libc_start_main ()
> (gdb) bt
> #0  0x000000000041cc03 in __libc_start_main ()
> #1  0x000000000040715a in _start () at ../sysdeps/x86_64/start.S:120
>
> We are using glibc-2.31 and gcc-9.2.0 if that makes a difference.
>
>   -- Bruce Dubbs
>      linuxfromscratch.org
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#40477: Segfault with grep-3.4 and pcre-8.44
>
>
>
>
> Date: 
>
> Mon, 21 Sep 2020 12:19:57 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
>
>
>
>
> On 4/6/20 8:31 PM, Bruce Dubbs wrote:
>
> > Upon more investigation my problem may be to be due to libsigsegv-2.12. If I 
> > keep that from being linked into grep it is fine.
>
> This appears to be the Gnulib/libsigsegv problem that Bruno Haible fixed 
> yesterday:
>
> https://lists.gnu.org/r/bug-gnulib/2020-09/msg00101.html
>
> so I'm closing the grep bug report.
>
>
> --- End Message ---