Pike-devel March 2021

pike-devel@lists.lysator.liu.se

7 participants
16 discussions

Pike Meet-up 2018-Q1
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 20 Oct '21

20 Oct '21

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 three month mark from the conference is coming up soon, it seems time to announce the first such meeting for 2018: Pike Meet-up 2018-Q1 Date: 2018-02-03 (Sat) Time: 10:00 - afternoon/evening Place: Roxen IS AB S:t Larsgatan 22A Linköping Welcome! /grubba

2 13

Compression.Lz4
by Stephen R. van den Berg 01 Apr '21

01 Apr '21

For the new CQL driver I need Lz4 support. Now, instead of introducing yet another toplevel Lz4 object, how about moving Bz2 and Gz and Lz4 into: Compression.Bz2 Compression.Gz Compression.Lz4 Any objections? -- Stephen.

4 5

Destructed objects inside a multiset?
by Stephen R. van den Berg 29 Mar '21

29 Mar '21

Do they need to be weeded out manually? If so, how? Or do they magically vanish and if so, when does that actually happen? -- Stephen.

1 0

make_static_string()
by Stephen R. van den Berg 20 Mar '21

20 Mar '21

Is it allowed/supported to put a string created with make_static_string() into an svalue and then give it to say the write() method of an arbitrary Stdio object? -- Stephen.

4 15

Shuffler revisited (2)
by Stephen R. van den Berg 18 Mar '21

18 Mar '21

In an attempt to prepare the Shuffler for use on the database connection in the pgsql module, I delved back into the Shuffler code again. This time I achieved 99.9% comprehension of the code. The result is a considerable rewrite of the inner loop. The rewrite was necessary because: a. The shuffle-source-management still had memory leaks. b. The size of the buffer writes was arbitrarily large (depending on the input block size). c. The way wrap_callback results were stored resulted in (only) mostly-correct data. d. The data of sources were used ever so briefly *after* getting freed. -- Stephen.

1 0

cmod compilation: Bad integer ordering in lower_or_pike_types()?
by Stephen R. van den Berg 18 Mar '21

18 Mar '21

Any clue as to what I messed up here? #### Making dynamic: post_modules/SQLite #### Making dynamic: post_modules/Shuffler match_types mismatch! a: zero b: void res: NULL tmp: zero tmp2: zero match_types mismatch! a: zero b: void res: NULL tmp: zero tmp2: zero pike_types_le mismatch! a: function(mixed:void) b: scope(0, or(function(zero:mixed)|__deprecated__(function(zero:void)))) res: 1 tmp: scope(0, and(or(function(mixed:void)|function(not(zero):void))&__deprecated__(function(not(zero):void)))) tmp2: scope(0, and(or(function(mixed:void)|function(not(zero):void))&__deprecated__(function(not(zero):void)))) low_type_binop(0x0002, function(mixed:void), scope(0, or(function(zero:mixed)|__deprecated__(function(zero:void)))), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) low_type_binop(0x0002, function(mixed:void), or(function(zero:mixed)|__deprecated__(function(zero:void))), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) low_type_binop(0x0002, function(mixed:void), function(zero:mixed), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) low_type_binop(0x0002, mixed, zero, 0x7fffb71ec3d0, 0x0200, 0x0200, 0x80) ret: not(zero) tmp: not(zero) low_type_binop(0x0002, function(:void), function(:mixed), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) low_type_binop(0x0002, void, void, 0x7fffb71ec3d0, 0x0300, 0x0300, 0x80) ret: NULL tmp: NULL low_type_binop(0x0002, void, mixed, 0x7fffb71ec3d0, 0x0100, 0x0000, 0x80) ret: void ret: function(:void) ret: or(function(mixed:void)|function(not(zero):void)) low_type_binop(0x0002, function(mixed:void), __deprecated__(function(zero:void)), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) low_type_binop(0x0002, function(mixed:void), function(zero:void), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) low_type_binop(0x0002, mixed, zero, 0x7fffb71ec3d0, 0x0200, 0x0200, 0x80) ret: not(zero) tmp: not(zero) low_type_binop(0x0002, function(:void), function(:void), 0x7fffb71ec3d0, 0x0000, 0x0000, 0x80) ret: NULL ret: function(not(zero):void) ret: __deprecated__(function(not(zero):void)) ret: and(or(function(mixed:void)|function(not(zero):void))&__deprecated__(function(not(zero):void))) ret: scope(0, and(or(function(mixed:void)|function(not(zero):void))&__deprecated__(function(not(zero):void)))) tmp3: scope(0, and(or(function(mixed:void)|function(not(zero):void))&__deprecated__(function(not(zero):void)))) /home/srb/pike/src/pike_types.cmod:3254: Fatal error: Bad integer ordering in lower_or_pike_types(). No stack - no backtrace. make[5]: *** [Makefile:94: override] Aborted make[4]: *** [Makefile:106: Shuffler] Error 1 make[3]: *** [Makefile:1182: post-modules-stamp] Error 1 make[2]: *** [Makefile:231: all] Error 2 make[1]: *** [Makefile:149: _make_in_builddir] Error 2 make: *** [Makefile:66: compile] Error 2 Closer inspection at /home/srb/pike/src/pike_types.cmod:3254 reveals that: min1 = 0 min2 = ffffffff max1 = 7fffffff max2 = 0 -- Stephen.

1 1

debugger-wip merge
by H William Welliver 16 Mar '21

16 Mar '21

Hello all- I’m planning on merging the work in progress debugger into master in the coming days. A prior version of this code has been reviewed and it is my understanding from Mateusz that there were 1 or 2 unaddressed items. I’ve addressed one (handling of multiple offsets for a given line) and don’t think the other item (in what file a particular set of functions belongs) makes sense at the moment, based on my read of the code. I wouldn’t however, be opposed to someone who feels more strongly about relocating it. I’ve made a few other minor enhancements to the C-level code that I don’t think negatively impact the outcome of that review. The first thing to know is that the debugger actually works[1]. My plan is to split the code into 2 or 3 parts: the C-level bits, the debugger itself which lives in lib/modules/Debug/Debugger.pmod and the bootstrap code in master.pike. When it lands, I’ll also have some instructions for how to try it out. My base assumptions (hopefully obvious but I’ll state them nonetheless): 1. When not enabled at runtime, it is intended that the code is not in the path of execution. 2. When enabled, the code should not cause aborts. 3. "Surprise" behavior is possible, some of which is known[2] and some not. 4. Performance is assumed to be impacted while debugging. Attempts to minimize the negative impact are obviously of interest. 5. Everything here is private/uncommitted and subject to change should something better rear its head. Some caveats: 0. This is very much work in progress, but I commit to minimize impact to others and get things to a point where that’s no longer the case as quickly as possible. I felt it important to get this code out in front of more people to look at and try. Specifically: 1. I’ve made a good faith effort to not commit known bugs, but I’m sure there are some and will investigate any problems identified. 2. There is vestigial code that I’ve left in place to ease the inevitable troubleshooting and confidence building that are coming. The plan is to remove them when they are no longer needed. 3. There is behavior that might be pared back (specifically related to breakpoints across a range of offsets, which may not be needed). 4. The Pike level code is where most of the action currently is, and is most likely to see major change. 5. Semi-related: there /seems/ to be a problem in LiveBacktraceFrame in that argument names aren’t available, and it appears they’re not making it out of the compiler intact. I haven’t been able to track down the source of that problem. Assistance would be welcome. If anyone sees a major problem in any of this, please let me know. Bill [1] http://wiki.gotpike.org/PikeDevel%2FPikeDebugger [2] http://wiki.gotpike.org/index.pike?page=PikeDevel/PikeDebuggerCaveats (will be in place by tomorrow)

2 1

Re: Did someone already try to ask someone at Lysator?
by Chris Angelico 15 Mar '21

15 Mar '21

On Mon, Mar 15, 2021 at 10:22 PM Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > Hi Stephen! > > > Did someone already try to ask someone at Lysator to push the power button? > > The power button wasn't the problem... > > The problem was due to the zpool version being bumped to a version not > supported by the version of GRUB on the bootdisks (Illumos bug 12780). > > That the hardware doesn't support booting the LiveUSB didn't help... > > We solved it by detaching the boot disk, putting it in a machine > that supported booting the LiveUSB, updating the boot block, and > then putting it back. > > Anyway, the machine has now been up for ~45 minutes. > > >I have, amongst other things, a fix for a fundamental data corruption bug > >in Stdio.Buffer which I fixed in master and in 8.0 waiting to be uploaded > >to the central git repository. > > The upstream repository should be fine now. > Thank you! Up and working. Very much appreciated. Now if I could just figure out how to implement generatorp()... ChrisA

1 0

Did someone already try to ask someone at Lysator?
by Stephen R. van den Berg 15 Mar '21

15 Mar '21

Did someone already try to ask someone at Lysator to push the power button? I have, amongst other things, a fix for a fundamental data corruption bug in Stdio.Buffer which I fixed in master and in 8.0 waiting to be uploaded to the central git repository. -- Stephen.

2 1

Multisets with duplicates?
by Stephen R. van den Berg 12 Mar '21

12 Mar '21

This seems like a bug: Pike v8.1 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > (<"foo", "bar">) | (<"some", "bar">); (1) Result: (< /* 3 elements */ "bar", "foo", "some" >) > (<"foo", "bar">) + (<"some", "bar">); (2) Result: (< /* 4 elements */ "bar", "bar", "foo", "some" >) > -- Stephen.

3 3

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