Re: [ID 20000121.004] [BUG t/lib/English.t 5.005_63] Segfault, probably due to tying.

[Gurusamy Sarathy <gsar@ActiveState.com>]

On Fri, 21 Jan 2000 13:06:47 EST, Michael G Schwern wrote:
>The segfault occurs on line 26:
>
>        print $PREMATCH, $MATCH, $POSTMATCH;
>
>$PREMATCH, $MATCH and $POSTMATCH at this point are all variables tied
>into English::Evil so I presume this is a tying problem and the stack
>trace seems to confirm that.
>
>Here is a stack trace from the point of the segfault.
>
>#0  0x400e8c25 in memmove () from /lib/libc.so.6
>#1  0x80c18de in Perl_sv_setpvn (sv=0x813f420, 
>    ptr=0x5 <Address 0x5 out of bounds>, len=5) at sv.c:2720
         ^^^

It would seem PL_curpm->op_pmregexp->subbeg is invalid at this point, but
the code passes it to sv_setpvn() without checking.

>#2  0x80a7d2f in Perl_magic_get (sv=0x813f420, mg=0x8193308) at mg.c:547
>#3  0x80a703b in Perl_mg_get (sv=0x813f420) at mg.c:96
>#4  0x80c084c in Perl_sv_setsv (dstr=0x813f42c, sstr=0x813f420) at sv.c:2452
>#5  0x80c598d in Perl_sv_mortalcopy (oldstr=0x813f420) at sv.c:4216
>#6  0x80e6e5e in Perl_pp_return () at pp_ctl.c:1819
>#7  0x80b223d in Perl_runops_debug () at run.c:56


Sarathy
gsar@ActiveState.com

---

References to:

Michael G Schwern <schwern@pobox.com>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---