Pike-devel November 2014

pike-devel@lists.lysator.liu.se

7 participants
12 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

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

visit to Linköping
by H. William Welliver III 09 Dec '14

09 Dec '14

I’ll be in Linköping visiting with Tobi and Company the weekend of December 5-7. If anyone is interested, perhaps we could broaden the scope to have more of a general Pike development meeting. Feel free to drop a note (this list is probably a fine place) if anyone’s interested! Bill

7 11

xenofarm?
by Stephen R. van den Berg 03 Dec '14

03 Dec '14

Xenofarm seems to have been out of order since a while, correct? -- Stephen.

6 7

Autodoc 8.1 complains about removed namespaces
by Stephen R. van den Berg 24 Nov '14

24 Nov '14

$ make doc Failed to move 7.6:: Failed to move 7.4:: When trying to fix that, I get lost in the autodoc/xml code. Anyone? -- Stephen.

6 10

gdb_backtraces()
by Mirar ＠ Pike developers forum 21 Nov '14

21 Nov '14

(gdb) p *Pike_interpreter_pointer Cannot access memory at address 0x0 is kind of suspicious, I take it?

1 1

Re: Autodoc 8.1 complains about removed namespaces
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 20 Nov '14

20 Nov '14

> >Well, I merely tied up the loose ends that were a natural result of >all compat support prior to 7.8 being ripped out already (not by me). >I.e. the functionality that *I* removed was already dead-in-the-water because >there was no way to call it anymore. > No, you could still call them. I kept them in because just because it was compatibility with old data, not old code.

3 2

crash
by Arne Goedeke 12 Nov '14

12 Nov '14

I attached a simple script which crashes pike. The code has cyclic dependencies within the same pmod, and ends up having parent_identifier=-1 in find_external_context. When compiled with debug, running pike -M lib test.pike results in the following backtrace. /home/el/code/rw/pike/src/interpret.c:778: Fatal error: Identifier out of range, loc->parent_identifer=-1! Backtrace at time of fatal: lib/Test.pmod/FOO.pmod:8: Test.A()->__INIT() lib/Test.pmod/module.pmod:5: Test.A()->__INIT() test.pike:3: /main()->main(1,({"/home/el/code/rw/pike_bugs/1/test.pike"})) Aborted Arne

1 0

cannot find input file: `wnotify_config.h.in'
by Stephen R. van den Berg 04 Nov '14

04 Nov '14

Compiling 8.1 on i386 stops at: configure: creating ./config.status config.status: creating make_variables config.status: creating Makefile config.status: error: cannot find input file: `wnotify_config.h.in' Any ideas? -- Stephen.

3 5

Re: Proposal: Enhance Process.run() to accept functions for stdout/stderr
by Chris Angelico 03 Nov '14

03 Nov '14

On Tue, Nov 4, 2014 at 1:25 AM, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > I'd prefer you didn't. Supposed to be stable and all... No probs. All sorted then. ChrisA

2 1

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 2014