Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Segfault generating src/post_modules/GL/auto.c on PowerPC
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 06 Dec '16

06 Dec '16

I noticed that Debian package builds of both 7.8(.866-7) and 8.0(.358-1) have recently started failing on the powerpc architecture. https://buildd.debian.org/status/fetch.php?pkg=pike8.0&arch=powerpc&ver=8.0… /«PKGBUILDDIR»/build/linux-3.16.0-4-powerpc64-ppc/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/«PKGBUILDDIR»/build/linux-3.16.0-4-powerpc64-ppc/master.pike /«PKGBUILDDIR»/src/post_modules/GL/gen.pike /«PKGBUILDDIR»/src/post_modules/GL/auto.c.in > auto.c.tmp Segmentation fault This doesn't happen when pike is compiled with -O0, and 7.8.866-6 built fine (the only difference is that -7 is built with MariaDB libraries instead of MySQL), so I assume a compiler bug, but perhaps someone can help figuring out what's triggering it. The backtrace is perhaps not terribly helpful (from 8.0.358): (gdb) bt full #0 jump_opcode_F_MARK_CALL_LFUN_AND_POP (arg1=272) at /home/zino/hack/pike8-rel/pike/src/interpret_functions.h:2418 addr = <optimized out> jumpaddr = <optimized out> #1 0xf7ceeb4c in ?? () No symbol table info available. #2 0x20462184 in mega_apply_low (args=args@entry=0, arg1=arg1@entry=0x206b6370, arg2=<optimized out>) at ./src/interpret.c:2721 saved_jmpbuf = <optimized out> uwp = {previous = 0xfffedc38, frame_pointer = 0x0, func = 0x204516a0 <restore_catching_eval_jmpbuf>, arg = 0x0} #3 0x204e4714 in call_pike_initializers (o=0x206b6370, args=args@entry=0) at ./src/object.c:338 p = 0x206b6370 #4 0x204e7b9c in get_master () at ./src/object.c:702 f = <optimized out> uwp = {previous = 0x0, frame_pointer = 0x0, func = 0x204e5b50 <get_master_cleanup>, arg = 0x0} inside = 1 #5 0x204e7f04 in debug_master () at ./src/object.c:720 o = <optimized out> #6 0x204d55cc in load_pike_master () at ./src/pike_embed.c:397 m = <optimized out> #7 0x2044724c in main (argc=6, argv=0xfffef534) at ./src/main.c:676 m = <optimized out> back = {previous = 0x0, recovery = {{__jmpbuf = {-1376152737, 0, 1917001823, 0 <repeats 13 times>, -134352256, -73784, 4, 543427968, -67736, 570426500, 0 <repeats 40 times>, -1, 0 <repeats 49 times>}, __mask_was_saved = 0, __saved_mask = {__val = {0 <repeats 32 times>}}}}, frame_pointer = 0x0, stack_pointer = 0, mark_sp = 0, severity = 40, onerror = 0xfffedbdc} e = <optimized out> num = <optimized out> p = 0xfffef767 ""

3 16

Callbacks in CMOD/C and error handling
by Pontus Östlund 03 Dec '16

03 Dec '16

So, I'm working on this libsass CMOD glue (a totally new world for me) and have a question: From the CMOD a callback in the Pike layer is called. If the Pike layer callback throws an error, how do I detect that in the CMOD? As it is now the error is thrown in the Pike layer and the backtrace is output to the console, but the C code after the callback still continues. How do I prevent this? Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

2 2

Arg.pmod changes incomplete?
by Stephen R. van den Berg 03 Dec '16

03 Dec '16

Pike 8.1 make doc results in: /var/src/roxen/81pike/lib/modules/Arg.pmod:623:Too many arguments to unknown function (expected 1 arguments). /var/src/roxen/81pike/lib/modules/Arg.pmod:623:Got : void | int. /var/src/roxen/81pike/lib/modules/Arg.pmod:632:Too many arguments to unknown function (expected 1 arguments). /var/src/roxen/81pike/lib/modules/Arg.pmod:632:Got : mixed. /var/src/roxen/81pike/lib/modules/Arg.pmod:641:Too many arguments to unknown function (expected 1 arguments). /var/src/roxen/81pike/lib/modules/Arg.pmod:641:Got : mixed. /var/src/roxen/81pike/lib/modules/Arg.pmod:754:Placeholder already has storage! /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:25:Undefined identifier Arg. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:25:Illegal program pointer. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:132:Must return a value for a non-void function. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:132:Expected: mixed. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:132:Got : void. Pike: Failed to load tool join_autodoc: Compilation failed. -- Stephen.

3 2

Segfault generating src/post_modules/GL/auto.c on PowerPC
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 01 Dec '16

01 Dec '16

>Are you saying that the compiler incorrectly optimized out the frame >pointer or that incorrect code led the compiler to believe that it >could optimize out the frame pointer? I'm saying that the machine code generator relies on the frame pointer (or similar construct) being present to implement the *_JUMP opcodes.

1 0

Refdoc
by Pontus Östlund 29 Nov '16

29 Nov '16

Hi guys! I saw the refdoc on the Pike site is somewhat broken. The plan is to port the new refdoc layout in 8.1 to 8.0, and I'm working on that as we speak. But in order to make that work I need to add the standalone Tools.Standalone.pike_to_html tool since that is used to highlight example code in the refdoc. Is that ok? Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

5 11

Segfault generating src/post_modules/GL/auto.c on PowerPC
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 29 Nov '16

29 Nov '16

For reference, Gentoo considers gcc 4.9.4 stable for all arches except x86 (where 4.9.3 is the latest stable). Anything beyond that is considered unstable.

1 0

EV_OOBAND etc. undefined in backend.cmod on Debian GNU/kFreeBSD
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 28 Nov '16

28 Nov '16

Sorry, I forgot that the build log doesn't show that bug but a earlier one caused by some clock problem causing src/configure to have a modification time in the future.

1 0

EV_OOBAND etc. undefined in backend.cmod on Debian GNU/kFreeBSD
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 28 Nov '16

28 Nov '16

Build on kfreebsd fails due to multiple undefined symbols; see https://buildd.debian.org/status/fetch.php?pkg=pike8.0&arch=kfreebsd-amd64&… It seems 6b9645e2708c53e92db4f752490f0d168280db10 introduced a bug among the #ifs in backend.cmod. At then line 2425, now line 2908, it did -#elif defined(BACKEND_USES_POLL) +#endif /* HAVE_SYS_DEVPOLL_H || HAVE_SYS_EPOLL_H */ + +#ifdef HAVE_POLL but then later we have #endif /* HAVE_POLL */ and then #elif defined(BACKEND_USES_KQUEUE) which doesn't match up with the other #ifdef BACKEND_USES_* conditionals any longer, so the KQUEUE part incorrectly gets omitted.

1 0

Buffer mode for SSL.File?
by H William Welliver III 25 Nov '16

25 Nov '16

Any plans to add buffer mode support to SSL.File? I just discovered this in Stdio.File and think it would be very nice if it were available here as well...

3 2

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1
by Chris Angelico 23 Nov '16

23 Nov '16

On Thu, Nov 24, 2016 at 12:40 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>In Python, it's done with a prefix - u"asdf" is a Unicode string, and >>b"asdf" is a byte string. > > Since nominally strings are Unicode (with the extended ISO 10646 > range) strings now, I think "asdf" can be left as the syntax for that, > and we only need a new syntax for the byte string ("buffer") type. We > can also look at Java, which has byte[] as the type for byte strings, > requiring literals like {'a','s','d','f'}, but I would like to see > something a bit more convenient to use. :-) Agreed. In Python 3.0+, that's how it is - an unadorned string is Unicode, and b"asdf" is a byte string. (Python 2.7 has it the other way - an unadorned string is bytes, and u"asdf" for Unicode - and because of that, you're allowed to put the prefixes on both types of string. But Pike needn't do that.) ChrisA

3 2

Jump to page:

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