broquaint has asked for the wisdom of the Perl Monks concerning the following question:
As far as I can tell this bug only affects v5.6.1 on linux, as I can't duplicate it on either Solaris using v5.6.1 or on linux using v5.005_03. If I do a gdb backtrace I get the followingshell> perldoc -q '$#' Segmentation fault (core dumped)
So the problem seems to lie in S_find_byclass which happens to be at line 850 in regexec.c in the v5.6.1 source. I'm not sure what the exact problem is, but I'm guessing it's something to do with the fact the # follows the $ which it probably shouldn't.(gdb) bt #0 0x080d2fb0 in S_find_byclass () at eval.c:41 #1 0x080d2ce4 in Perl_re_intuit_start () at eval.c:41 #2 0x0809b6f3 in Perl_pp_match () at eval.c:41 #3 0x080990d8 in Perl_runops_standard () at eval.c:41 #4 0x0805c5f3 in S_run_body () at eval.c:41 #5 0x0805c342 in perl_run () at eval.c:41 #6 0x08059fd0 in main () at eval.c:41 #7 0x40073177 in __libc_start_main (main=0x8059f60 <main>, argc=4, ub +p_av=0xbffff8fc, init=0x8059194 <_init>, fini=0x80dfa00 <_fini>, rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffff8ec) at ../sysde +ps/generic/libc-start.c:129
If this particular bug hasn't been reported yet (and I don't think it has, as I couldn't find it on perlbug), how would I go about reporting it?
broquaint
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: perldoc core dump bug
by rinceWind (Monsignor) on Feb 25, 2002 at 11:13 UTC | |
Re: perldoc core dump bug
by Chmrr (Vicar) on Feb 25, 2002 at 11:45 UTC | |
Re: perldoc core dump bug
by broquaint (Abbot) on Feb 25, 2002 at 11:25 UTC | |
Re: perldoc core dump bug
by Veachian64 (Scribe) on Feb 25, 2002 at 13:04 UTC |