Pike-devel April 2020

pike-devel@lists.lysator.liu.se

4 participants
14 discussions

Build failure on macOS (HEAD of master)
by Marc Simpson 01 May '20

01 May '20

Hi all, FYI, it looks like master no longer builds on macOS due to the MTU additions in [44f12ac]: .../src/modules/_Stdio/file.c:5526:16: error: use of undeclared identifier 'IP_MTU' int option = IP_MTU; .../src/modules/_Stdio/file.c:5541:14: error: use of undeclared identifier 'IPV6_MTU' option = IPV6_MTU; Best, Marc

1 1

SQLite query segfaults
by Marc Simpson 30 Apr '20

30 Apr '20

Hi folks, It seems that I can reliably segfault recent Pike 8.1 installs when using sprintf-style SQLite queries: $ echo ' create table demo(a, b); insert into demo(a, b) values(1, "abc")' | sqlite3 demo.db $ pike Pike v8.1 release 13 running Hilfe v3.5 [...] > Sql.Sql db = Sql.Sql("sqlite://demo.db"); > db->query("select * from demo"); (1) Result: ({ /* 1 element */ ([ /* 2 elements */ "a": "1", "b": "abc" ]) }) > db->query("select * from demo where a = :a", ([":a": 1 ])); (2) Result: ({ /* 1 element */ ([ /* 2 elements */ "a": "1", "b": "abc" ]) }) > db->query("select * from demo where a = %d", 1); Segmentation fault This occurs on both macOS and Linux; on macOS, segfaults are observed when the SQLite module is linked against either MacPorts' SQLite 3 or the system wide dylib in /usr/lib. Note that query() with a mapping argument doesn't segfault; furthermore, no such segfault occurs under Pike v8.0 release 702. Please let me know whether this is reproducible (and/or whether more information is required). Thanks, Marc

3 4

Interest in zip archive resolver?
by H William Welliver 29 Apr '20

29 Apr '20

Hello all, I’ve been going through some of my long ignored feature branches and found a few that might have promising code. Is there any interest in being able to specify (include/program/module) paths in terms of zip archives? At one point I wanted to be able to provide an entire application as a single file, and wrote support for various paths inside of zip files. The code I wrote is about 7 years old, but it was/is used and I’d be happy to fix it up if no one has major objections. The code in question provides support for including zip files as part of paths for -I, -P and -M: pike -M /path/to/some.zip or pike -M /path/to/some.zip/folder As well as the idea of a properly formatted archive with well know directories for modules, includes and programs: pike -A /path/to/some.zip where some.zip looks like: include/* modules/* And implicitly sets -I, -M and -P to include/, modules and / respectively. Any thoughts, opinions, suggestions? Bill

3 2

Re: Interest in zip archive resolver?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 17 Apr '20

17 Apr '20

>I hadn.FN"t really thought of making it executable$B!D(B I think thereN"s a >magic cookie at the beginning of a ZIP file so a hashbang might not >work if the archive were intended to be spec-compliant. No, the magic cookie (PK\005\006) is at the _end_. The central directory and file entries also have magic cookies (PK\001\002 and PK\003\004 respectively), but those don't have to be at any specific position but are pointed out as file offsets rooted in the PK\005\006 header at offset file_size-22. AFAICR it was standard practice to make self-extracting ZIP:s on MS-DOS by just cramming an MZ binary before the archive (and adjusting the offsets accordingly). It should be pretty easy to just put something at the start if creating the archive by hand like Filesystem.Zip is doing.

1 0

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 2020