Pike-devel April 2019

pike-devel@lists.lysator.liu.se

5 participants
13 discussions

Re: Pike Meet-up 2019-Q2
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 24 Apr '19

24 Apr '19

>Any chance it might be moved to 11th May? Sure, I don't have any problem with either date. What do others say? >År., 17 kwi 2019 o 11:53 Henrik GrubbstrÃ¶m (Lysator) @ Pike (-) developers >forum <10353(a)lyskom.lysator.liu.se> napisaÅ(a): > >> Hi. >> >> At Pike Conference 2017 it was decided that we ought to hold a >> more informal meeting in LinkÃ¶ping ~ once every quarter. As the >> six month mark from the latest conference is coming up soon, >> it seems time to announce the second such meeting for 2019: >> >> Pike Meet-up 2019-Q2 >> Date: 2018-05-04 (Sat) >> Time: 10:00 - afternoon/evening >> Place: Roxen IS AB >> S:t Larsgatan 22A >> LinkÃ¶ping /grubba

2 1

Re: Interaction between automap and argument splicing segfaults
by Chris Angelico 04 Apr '19

04 Apr '19

On Thu, Apr 4, 2019 at 11:11 PM Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > > The crash is on this line: > [...] > > If pike is built with PIKE_DEBUG, you get this fatal instead: > [...] > > So the crash is in the compiler proper, not in the execution of the > > program. > > Thanks for the report, test case and investigation. > > Fixed the code generator in Pike 8.0 and master. > Thanks! Confirming that it works with my original code too (from which the test case was derived). Much appreciated! ChrisA

1 0

Interaction between automap and argument splicing segfaults
by Chris Angelico 04 Apr '19

04 Apr '19

Test case: int score_image(string image, int r, int g, int b) {return 42;} array(int) getpixel() {return ({1, 2, 3});} int main(int argc, array(string) argv) { if (argc < 2) exit(0, "All good! Try again with -DBOOM for a segfault.\n"); array images = ({"foo", "bar", "quux"}); for (int x = 0; x < 10; ++x) //Without the loop, no boom { #ifdef BOOM array pixel = getpixel(); array(int) scores = score_image(images[*], @pixel); //Segfault #else [int r, int g, int b] = getpixel(); array(int) scores = score_image(images[*], r, g, b); //But avoiding @ works. #endif } } It's fine with either [*] or @pixel, and it's even fine with both, as long as it's not in a loop. But put all three together, and the interpreter segfaults before executing a single line of actual code, which I suspect means an issue at the compilation stage. (Can be triggered identically by casting "boom.pike" to program too.) Tested with the latest master branch, and with 8.0.735. No idea where to start looking for the cause, but it's a completely consistent crash. ChrisA

3 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel April 2019