Re: Tin 1.9.0 core dump

On Fri, Mar 10, 2006 at 09:58:11AM +0100, Maurizio Matteo Munafo' wrote:

[tin 1.9.0 and bundled pcre-6.6]

> Thanks. I knew that was not going to be enough, but I did not know how to
> generate the relevant information.
> 
> This is the trace result...
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0 in ?? ()
> (gdb) bt
> #0  0x0 in ?? ()
> #1  0x8099bc1 in pcre_compile2 ()
> #2  0x8098bed in pcre_compile ()
> #3  0x8086e31 in compile_regex (
>     regex=0x80e2aaf "(R[eE](\\^\\d+|\\[\\d\\])?|A[wW]|Odp):\\s",
>     cache=0x8122c04, options=16) at ./regex.c:124

looks ok to me (but could be optimized as it's done in the newwer version)

> #4  0x806403e in postinit_regexp () at ./init.c:922
> #5  0x806c1a8 in main (argc=3, argv=0xbffff564) at ./main.c:217
> 
> 
> So, a problem in the new PCRE version... and a strip_re_regex value in the
> tinrc file that can be REALLY old...
> 
> But after removing the tinrc file and creating a new one with tin 1.8.1
> I still get the core dump and the trace
> Program received signal SIGSEGV, Segmentation fault.
> 0x0 in ?? ()
> (gdb) bt
> #0  0x0 in ?? ()
> #1  0x8099bc1 in pcre_compile2 ()
> #2  0x8098bed in pcre_compile ()
> #3  0x8086e31 in compile_regex (
>     regex=0x80e2aaf "(?:R[eE](?:\\^\\d+|\\[\\d\\])?|A[wW]|Odp|Sv):\\s",
>     cache=0x8122c04, options=16) at ./regex.c:124
> #4  0x806403e in postinit_regexp () at ./init.c:922
> #5  0x806c1a8 in main (argc=3, argv=0xbffff564) at ./main.c:217

again, looks ok. strange. I'll ask the other tin-dev folks if they have an
idea.

urs
-- 
"Only whimps use tape backup: _real_ men just upload their important stuff
 on ftp, and let the rest of the world mirror it ;)" - Linus