Pike-devel April 2015

pike-devel@lists.lysator.liu.se

2 participants
6 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 03 Dec '25

03 Dec '25

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

3 2

Re: Setting socket options: so many, uhh, options!
by Chris Angelico 15 Sep '16

15 Sep '16

On Tue, Mar 10, 2015 at 10:05 PM, Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Wait, I said REUSEPORT? What's the difference to REUSEADDR? Mysteries > of TCP sockets... Here's a decent explanation, I think: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and… ChrisA

3 6

8.0 dmalloc doesn't build
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 17 Apr '15

17 Apr '15

Trying to compile Pike 8.0 --with-dmalloc gives me this: make[4]: Entering directory `/home/nilsson/pike/dmalloc/post_modules/GL' /home/nilsson/pike/dmalloc/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/nilsson/pike/dmalloc/master.pike /home/nilsson/pike/src/post_modules/GL/gen.pike /home/nilsson/pike/src/post_modules/GL/auto.c.in > auto.c.tmp Segmentation fault make[4]: *** [auto.c] Error 139 I don't know this code at all. Program received signal SIGSEGV, Segmentation fault. read_int (offset=1) at /home/nilsson/pike/src/docode.c:180 180 { (gdb) bt #0 read_int (offset=1) at /home/nilsson/pike/src/docode.c:180 #1 0x080ef9f7 in do_code_block (n=0x975bee8) at /home/nilsson/pike/src/docode.c:2896 #2 0x082829f8 in dooptcode (name=0x964b340, n=0x975bee8, type=0x9621090, modifiers=1) at /home/nilsson/pike/src/las.c:5282 #3 0x0806031f in yyparse () at language.yacc:920 #4 0x081d635c in run_pass2 (c=0x968f730) at /home/nilsson/pike/src/program.c:9146 #5 0x081d6c48 in f_compilation_compile (args=0) at /home/nilsson/pike/src/program.c:9658 #6 0x08097cc3 in lower_mega_apply (args=0, o=0x94885f4, fun=<value optimized out>) at /home/nilsson/pike/src/interpret.c:2172 #7 0x080981bb in mega_apply_low (args=0, arg1=0x94885f4, arg2=1) at /home/nilsson/pike/src/interpret.c:2719 #8 0x081ad551 in f_compilation_env_compile (args=1) at /home/nilsson/pike/src/program.c:8672 #9 0x08097cc3 in lower_mega_apply (args=1, o=0x94885bc, fun=<value optimized out>) at /home/nilsson/pike/src/interpret.c:2172 #10 0x080981bb in mega_apply_low (args=1, arg1=0x94885bc, arg2=1) at /home/nilsson/pike/src/interpret.c:2719 #11 0x082890b2 in f_compile (args=1) at /home/nilsson/pike/src/builtin_functions.c:4636 #12 0x081875a4 in get_master () at /home/nilsson/pike/src/object.c:634 #13 0x08160a7c in load_pike_master () at /home/nilsson/pike/src/pike_embed.c:399 #14 0x0805a503 in main (argc=6, argv=0xbffff594) at /home/nilsson/pike/src/main.c:676

1 0

Address sanitizer
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 13 Apr '15

13 Apr '15

Could we use -fsanitize=address to remove most of the debug malloc code?

2 1

Pikefarm revived.
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Apr '15

13 Apr '15

FYI: I've spent the last few days updating Pikefarm to current Xenofarm and to monitoring git and the current branches of Pike. It now seems to work again. Caveat: The put binary in Xenofarm does not support redirects, so the resulturl needs to be updated to pike.lysator.liu.se.

2 1

SSL curve ciphers
by Chris Angelico 06 Apr '15

06 Apr '15

See branch: rosuav/curve_crypto_guard Is there a simpler way to cope with crypto absences than all the #if'ing everywhere? It's easy to create a Pike that won't build on systems that lack one or other. ChrisA

3 2

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 2015