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

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.

Occasional hiccups during https negotiations with Google

Not consistently, but once every 10 tries or so, I get the following backtrace which does not seem to originate in my own code: Can not modify the buffer right now, there are active subbuffers. -:1: _static_modules._Stdio()->Buffer(0 bytes, read=[..-1] data=[0..-1] free=[0.. 5300]

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: >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: > >>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

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: >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?): [...] > Program

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: Occasional hiccups during https negotiations with Google

Stephen R. van den Berg wrote: >Not consistently, but once every 10 tries or so, I get the following >backtrace which does not seem to originate in my own code: Might it be triggered by an HTTP keep-alive session terminating? My normal program logic works fine, so all API-sessions I have with

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

> >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

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.