Pike-devel November 2017

pike-devel@lists.lysator.liu.se

7 participants
42 discussions

autoconf and ac_tool_prefix
by H. William Welliver III 22 Nov '17

22 Nov '17

I’ve noticed that there are a number of checks like this in various configure.ins: MY_AC_PATH_PROG(FT_CONFIG, ${ac_tool_prefix}freetype-config, no) The pkgsrc framework automatically sets the --host option (among other things) on configure, which causes ac_tool_prefix to be set to something like x86_64-sun-solaris2.11. The problem is that in this case (and others), there is no x86_64-sun-solaris2.11-freetype-config, only freetype-config. That causes a lot of dependencies to be left unfound, which isn’t ideal. I notice that the check for gcc falls back to gcc, so it’s possible there’s a bug in autoconf itself. Would anyone care to offer an opinion as to the proper solution to this problem? I could create a bunch of symlinks, but that doesn’t seem like the best way to solve this (though it might be the quickest). Bill

2 1

dmalloc issue
by Martin Nilsson (Coppermist) ＠ Pike (-) developers forum 22 Nov '17

22 Nov '17

I currently get the following with Pike 8.1 with debug: nilsson@carbon:~/pike/dmalloc$ make run_hilfe /home/nilsson/pike/dmalloc/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/nilsson/pike/dmalloc/master.pike Pike v8.1 release 9 running Hilfe v3.5 (Incremental Pike Frontend) Terminal closed. Strings left: 1 (65616 bytes) (zapped) 0x0x45d6ce0: 3 refs, len=0, size_shift=0, hval=0x (0) "" ==LEAK==: (0x45e9cb0) 2 bytes **Block: 0x45e9cb0 Type: PIKE_T_UNKNOWN Refs: -2088959992 **Cannot describe block of type PIKE_T_UNKNOWN (247) ******************* Locations that handled 0x45e9cb0: (gc generation: 0/6 gc pass: 0/0) *** /home/nilsson/pike/src/interpret_functions.h:3095 xalloc (1 times) !*! *** /home/nilsson/pike/src/pike_memory.c:356 malloc (1 times) Not much help in the printout to pin it down.

3 7

Interactive debugging and live data inspection
by Stephen R. van den Berg 22 Nov '17

22 Nov '17

I just checked in a debugging aid I created to be able to do some live data inspection in running Pike programs (I used it to find the cause of a deadlock in pgsql). I'd appreciate feedback on the implementation and usability of Debug.Peek (in Pike 8.1). To get a rough impression of what it does, here's an excerpt out of the documentation: ------------------------------------------------ Class Debug.Peek Description Allows for interactive debugging and live data structure inspection in both single- and multi-threaded programs. Creates an independent background thread that every pollinterval will show a list of running threads. Optionally, a triggersignal can be specified which allows the dump to be triggered by signal. Example: In the program you'd like to inspect, insert the following one-liner: Debug.Peek("/tmp/test.pike"); Then start the program and keep it running. Next you create a /tmp/test.pike with the following content: void create() { werror("Only once per modification of test.pike\n"); } int main() { werror("This will run every iteration\n"); werror("By returning 1 here, we disable the stacktrace dumps\n"); return 0; } void destroy() { werror("destroy() runs just as often as create()\n"); } Whenever you edit /tmp/test.pike, it will automatically reload the file. ------------------------------------------------ -- Stephen.

3 4

string_assignment
by Martin Nilsson (Coppermist) ＠ Pike (-) developers forum 22 Nov '17

22 Nov '17

I'm looking at init_string_assignment_storage() in operators.c that initialized the object used when assigning individual characters in a string. Since the object is created with low_clone() the C init function is never called, so this code is currently not active. Since the object storage is zeroed, not calling the initializer is typically fine, but this initializer does SET_SVAL(THIS->lval[0], T_INT, PIKE_T_FREE, integer, 0); where PIKE_T_FREE isn't 0, so enabling this code would make a difference. However, all uses of PIKE_T_FREE in svalue.c looks for TYPEOF(x)==PIKE_T_FREE, not SUBTYPEOF(x). What is the desired behaviour here?

3 8

Concurrent
by Martin Nilsson (Coppermist) ＠ Pike (-) developers forum 22 Nov '17

22 Nov '17

Anyone against putting the (pike code only) Concurrent module in 8.0.

2 3

C-c
by Martin Nilsson (Coppermist) ＠ Pike (-) developers forum 22 Nov '17

22 Nov '17

There is an annoying difference between Pike 8.0 and 8.1. If you start hilfe Pike 8.0 will exit as soon as you press ctrl-C. In 8.1 Pike doesn't exist until it get one more key press. Why is that?

3 5

CERT C
by Martin Nilsson (Coppermist) ＠ Pike (-) developers forum 22 Nov '17

22 Nov '17

I found some interesting recommendations from CERT on secure C coding that perhaps would be interesting to apply. https://www.securecoding.cert.org/confluence/display/c/3+Recommendations

1 0

Garbage i Pike core?
by Jonas Walld�n ＠ Pike developers forum 22 Nov '17

22 Nov '17

Vi pratar en del om GC-körningar i CMS/EP i Slack, och på en i stort sett obelastad EP hos Kvällsstunden stack detta ut i manuell GC-körning: src/pike_search.c:197 _static_modules.Builtin()->Sear... 22 9 -24 148464 Är det någon intern optimering av (sträng?)sökning som läcker garbage vid normal användning?

1 1

Proposal: Create Stdio.Port from systemd-provided socket
by Chris Angelico 22 Nov '17

22 Nov '17

Branch: rosuav/systemd-sockets Currently, you can create a Stdio.Port("stdin") as a means of accepting a socket handed to you as FD 0. However, there's no way to accept a socket given as any other FD, making it impossible to use this for systemd's sockets. Example: $ cat /etc/systemd/system/listendemo.service [Unit] Description=Listen Demo Requires=listendemo.socket [Service] User=rosuav ExecStart=/usr/local/bin/pike /home/rosuav/listendemo.pike WorkingDirectory=/home/rosuav $ cat /etc/systemd/system/listendemo.socket [Socket] ListenStream=123 $ cat listendemo.pike object mainsock = Stdio.Port("systemd", acceptloop); void acceptloop() { while (object sock=mainsock->accept()) { write("Accepted sock: %O\n", sock); sock->write("Stub\n"); sock->close(); } } int main() { write("Main sock: %O\n", mainsock); return -1; } Note that the "User=rosuav" directive means that Pike is run as a non-root user. This spares the application the hassle of managing privileges securely, as it never gets root privileges (assuming, of course, that the only reason it needed root was to bind to a privileged port, which is true for a lot of programs). As with "stdin" mode, the second parameter is optional (blocking vs nonblocking). This won't break on non-systemd systems for two reasons: firstly, all it ever does is query environment variables, and secondly, it does this only if the application requests it explicitly, so you have to actually ask for it. Is this something that would be useful? Feel free to bikeshed the API - it's not in 8.1 yet, so anything can change. ChrisA

3 6

PostgreSQL pgsql driver: the dust has settled
by Stephen R. van den Berg 22 Nov '17

22 Nov '17

After some extreme hacking and debugging, the dust around the pgsql driver has finally settled. The fixes mostly concern rare conditions when the driver is being (ab)used while under heavy error rates from the database, cancelling random queries, dropping and/or destructing objects willy-nilly. It passes all tests that I have with flying colours now, no exceptions. People using PostgreSQL are invited to test the improved driver (both in Pike 8.0 and in Pike 8.1). -- Stephen.

1 0

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