Pike-devel January 2015

pike-devel@lists.lysator.liu.se

4 participants
7 discussions

Setting socket options: so many, uhh, options!
by Chris Angelico 10 Mar '15

10 Mar '15

Topic branch: rosuav/sockopt Per Lance's suggestion, I've made a generic setsockopt() function. It works only with integers, so it's not suitable for SO_LINGER, which therefore should stay the way it is (linger() takes a magic parameter of -1), but it works for any of the simple boolean options. As to shortcut functions, though, there are a few ways they can be done. 1) set_keepalive() always exists, even if SO_KEEPALIVE isn't available. If you call it when there's no SO_KEEPALIVE, it sets errno and returns failure. 2) set_nodelay() exists only if TCP_NODELAY is available. 3) setsockopt() itself is useless without the constants, and Stdio.TCP_NODELAY will exist only if TCP_NODELAY is available. So in a Pike script, using setsockopt() requires either has_index() run-time checks or #if compile-time checks for the options you want; set_keepalive's model works easily if you know that the Pike version you're targeting supports it; and set_nodelay's model lets you treat older Pikes and systems without that feature the same way. I'd rather make it as easy as possible on the Pike code. Which way makes more sense? ChrisA

5 13

cycle detection and destroy()
by Arne Goedeke 20 Feb '15

20 Feb '15

The destruction of objects is deferred. this leads to destroy() being called at some later point (after error, function return, some io handling, etc). when destroy() calls any code which has cycle detection, this can lead to spurious errors. Imagine a destroy function which calls sprintfs with some global object (e.g. Val.null). Similar problems arise when destroy is called while some mutex lock is being held and destroy() tries to aquire the same lock. Of course in that case the cycle detection simply guards against deadlock. What kinds of things can safely be done from within destroy() and should we document them? arne

4 3

gdb_backtraces()
by Mirar ＠ Pike developers forum 10 Feb '15

10 Feb '15

Should gdb_backtraces() still work in 8.0? (gdb) call gdb_backtraces() Program received signal SIGSEGV, Segmentation fault. 0x0005e0c4 in gdb_backtrace (thread_id=<optimized out>) at /home/pi/Pike-v8.0.10/src/interpret.c:3345 3345 args = DO_NOT_WARN((INT32) MINIMUM(f->num_args, Pike_sp - f->locals)); The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on". Evaluation of the expression containing the function (gdb_backtraces) will be abandoned. When the function is done executing, GDB will silently stop. (gdb) p *f $2 = {refs = 1, args = 1, fun = 9, num_locals = 1, num_args = 1, flags = 0, ident = 0, next = 0x1f7bd84, scope = 0x0, pc = 0x0, return_addr = 0x200336f "\024\217-", locals = 0xb6ac5098, save_sp = 0xb6ac5090, expendible = 0xb6ac5098, save_mark_sp = 0xb6a63000, mark_sp_base = 0xb6a63000, current_object = 0x1f78608, current_program = 0x1f726ec, context = 0x1f858dc, current_storage = 0x1f8ef50 "`\357\370\001\003"} (gdb) p *Pike_interpreter_pointer Cannot access memory at address 0x0 (gdb) info threads Id Target Id Frame * 2 Thread 0xb65c4470 (LWP 19748) "pike" 0xb6e9e250 in nanosleep () from /lib/arm-linux-gnueabihf/libpthread.so.0 1 Thread 0xb6fde000 (LWP 19742) "pike" 0x0005e0c4 in gdb_backtrace (thread_id=<optimized out>) at /home/pi/Pike-v8.0.10/src/interpret.c:3345 Both threads look like normal pike interpreter threads, except the one with the crashed gdb_backtraces() on top. This is repeatable, but not from just running Hilfe. ARM (Pi).

3 3

VALS Semester of Code - project pike packaging
by Martin Bähr 12 Jan '15

12 Jan '15

(resend with the right subject, sorry) hi, i am a mentor at FOSSASIA which has been accepted as a mentor organisation for VALS Semester of Code. You can read more about this program at http://semesterofcode.com/ and http://vps2.semesterofcode.com One of the projects i am proposing is to build pike packages for all major linux distributions. This may not be much for a 3 month project, but i expect the student to work on submitting the packages, so they not only need to run, but follow the distributions requirements. I'd like to invite pike developers to join me as mentors for this project, and also offer you to mentor other pike related projects. Registration for mentors is by invitation, so if you are able to mentor projects please send me an email with details about projects you would like to mentor. We only have a short time to register mentors and list projects, so please reply as soon as you can. The name of the project Describe the project At a minimum, please include the expected outcome of the project, a potential mentor, the skills and/or languages required to complete the project, and a general "difficulty" level. The project should take about 3 months to complete. Please bear in mind that it's better to start with a smaller project that can be extended if your student proves to be capable rather than have an over-ambitious idea which can't be completed in time. The url of this project This could be for example a link to a bug tracker issue or google doc that describes the project idea. Some tags to facilitate searching (Delimited by comma i.e. php, javascript, html) greetings, martin. -- eKita - the online platform for your entire academic life -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/

1 0

VALS Semester of Code - project use-mail
by Martin Bähr 12 Jan '15

12 Jan '15

hi, i am a mentor at FOSSASIA which has been accepted as a mentor organisation for VALS Semester of Code. You can read more about this program at http://semesterofcode.com/ and http://vps2.semesterofcode.com One of the projects i am proposing is to build pike packages for all major linux distributions. This may not be much for a 3 month project, but i expect the student to work on submitting the packages, so they not only need to run, but follow the distributions requirements. I'd like to invite pike developers to join me as mentors for this project, and also offer you to mentor other pike related projects. Registration for mentors is by invitation, so if you are able to mentor projects please send me an email with details about projects you would like to mentor. We only have a short time to register mentors and list projects, so please reply as soon as you can. The name of the project Describe the project At a minimum, please include the expected outcome of the project, a potential mentor, the skills and/or languages required to complete the project, and a general "difficulty" level. The project should take about 3 months to complete. Please bear in mind that it's better to start with a smaller project that can be extended if your student proves to be capable rather than have an over-ambitious idea which can't be completed in time. The url of this project This could be for example a link to a bug tracker issue or google doc that describes the project idea. Some tags to facilitate searching (Delimited by comma i.e. php, javascript, html) greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/

1 0

Mail gateway stuck again?
by Stephen R. van den Berg 05 Jan '15

05 Jan '15

Anyway, I just tested the threading problem on 8.0. Comparable (fatal) results. -- Stephen.

2 4

external module building in pike 8
by Arne Goedeke 02 Jan '15

02 Jan '15

The dependency changes in 1026020eca50ea873efc94a6b16a6ecbf2dff34c break external cmod building for me. Do we need an external equivalent to dynamic_module_makefile ?

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