Segfault from Pike 8.1 - possible type check issue?

> float thing_sum(array(string) things) { > return `+(@(array(float))things) + 1.0; > } I can't reproduce the issue with a current Pike 8.1, but there have been lots of fixes to the type checker the last few months. /grubba

Segfault from Pike 8.1 - possible type check issue?

float thing_sum(array(string) things) { return `+(@(array(float))things) + 1.0; } Without the "+ 1.0" at the end (or some other arithmetic operation), it doesn't bomb out. GDB is pointing to src/pike_types.cmod:11185 which is just an assignment, but I suspect the issue is the add_ref above

Type checking segfault in Pike 8.1

void boom(mapping info) {m_delete(info[0]);} It ought to give a compilation error (not enough args to m_delete) but it segfaults the interpreter on compilation. Correct behaviour is restored if the argument is explicitly cast to mapping: void boom(mapping info) {m_delete((mapping)info[0]);}

Re: SEGFAULT in Pike 8.1

Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >Stephen R. van den Berg wrote: >> >Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >> >>Now please fix the testsuite falures caused by the Stdio.FakePipe changes. >> >I'll run through them. >> Fixed. >There are still

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: > >Henrik Grubbström (Lysator) @ Pike (-) developers forum wrote: > >>Now please fix the testsuite falures caused by the Stdio.FakePipe changes. > > >I'll run through them. > > Fixed. There are still some failures that are triggered: | Doing tests in

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: >Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >>Now please fix the testsuite falures caused by the Stdio.FakePipe changes. >I'll run through them. Fixed. -- Stephen.

Re: SEGFAULT in Pike 8.1

Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >Now please fix the testsuite falures caused by the Stdio.FakePipe changes. I'll run through them. -- Stephen.

Re: SEGFAULT in Pike 8.1

> >Looks like something has set Pike_compiler->new_program to NULL. > > >New attempt at fixing committed. > > $ pike -e "foo::bar = 1;" > -:2:No inherit or surrounding class foo. > Compilation failed. > > Cheers! Great. Now please fix the testsuite falures caused by the Stdio.FakePipe changes.

Re: SEGFAULT in Pike 8.1

Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >> Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >> >Thanks. Potentially fixed. >Looks like something has set Pike_compiler->new_program to NULL. >New attempt at fixing committed. $ pike -e "foo::bar = 1;" -:2:No

Re: SEGFAULT in Pike 8.1

> Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: > >Thanks. Potentially fixed. > > Sorry, whack-a-mole, I guess. The bug shifted, maybe it's more obvious now > (you check for inh > 0, does that even work for pointers? Maybe that > should be inh != 0 instead?): [...] > Program

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: >Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >>Thanks. Potentially fixed. >Sorry, whack-a-mole, I guess. The bug shifted, maybe it's more obvious now >(you check for inh > 0, does that even work for pointers? Maybe that >should be inh != 0

Re: SEGFAULT in Pike 8.1

Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >Thanks. Potentially fixed. Sorry, whack-a-mole, I guess. The bug shifted, maybe it's more obvious now (you check for inh > 0, does that even work for pointers? Maybe that should be inh != 0 instead?): -:2:No inherit or surrounding

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: >Program received signal SIGSEGV, Segmentation fault. >0x5561c6b5 in find_inherited_identifier (inherit_state=0x557e7140, >inherit_depth=0, inh=1, ident=0x5590a308) >at /var/src/roxen/81pike/src/program.c:2304 >2304 return

Re: SEGFAULT in Pike 8.1

Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >Stephen R. van den Berg wrote: >> >>Please provide a full example. >> Shortest example so far: >> $ pike -e "foo::bar = 1;" >> -:2:No inherit or surrounding class foo. >> Segmentation fault >I can't reproduce the crash: >| $

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: > >>Please provide a full example. > > Shortest example so far: > > $ pike -e "foo::bar = 1;" > -:2:No inherit or surrounding class foo. > Segmentation fault I can't reproduce the crash: | $ ./pike -e "foo::bar = 1;" | -:2:No inherit or surrounding class foo. |

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: >>Please provide a full example. Shortest example so far: $ pike -e "foo::bar = 1;" -:2:No inherit or surrounding class foo. Segmentation fault -- Stephen.

Re: SEGFAULT in Pike 8.1

Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: >> When I run the following in Pike 8.1, it SEGFAULTs: >> foo::bar = 1; >> Gets me: >> p.pike:4:No inherit or surrounding class foo. >> Segmentation fault >Please provide a full example. $ ls -l p.pike -rwxr-xr-x 1 srb srb 39 jun

SEGFAULT in Pike 8.1

> When I run the following in Pike 8.1, it SEGFAULTs: > > foo::bar = 1; > > Gets me: > p.pike:4:No inherit or surrounding class foo. > Segmentation fault Please provide a full example. /grubba

SEGFAULT in Pike 8.1

When I run the following in Pike 8.1, it SEGFAULTs: foo::bar = 1; Gets me: p.pike:4:No inherit or surrounding class foo. Segmentation fault -- Stephen.