Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

DEBUG_MALLOC
by Arne Goedeke 30 Jun '13

30 Jun '13

I was trying to replace the BLOCK_ALLOC usage in pike_memory.c DEBUG_MALLOC mode. Unfortunately, since it uses the block allocator in its malloc tracer, which in turn calls malloc, that results in a deadlock. From what I can tell, that problem was already present when using the old "block_alloc.h", but it wasnt triggered since memory pages are preallocated. Before I try to work around that: What kinds of malloc misuses and memory access errors will DEBUG_MALLOC actually detect, which valgrind won't? Is it something we want to keep? arne

2 1

Pike 8
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 17 Jun '13

17 Jun '13

This Saturday we had a short (6 hours) Pike meeting in Linköping where we discussed what we would like to do with the langauge for the near future. The two topics were basically (besides trading ideas and discussions in general) what we need to do to make the next release in shortest amount of time, and what we would like to do for the next immediate release. The consensus was to attempt to push for a 8.0 release, given the large amount of changes since 7.0, and to make that release with the current feature set. The task list for that on a high level is - Fork a 8.0 and next branch (9.0?) soonish (within a week?) - Fix compilation issues. This basically boils down to a requirement on version 4 of GCC and to remove redundant configure tests that today prevents correct behavior. - Fix the testsuite. There are not very many issues that needs to be fixed, but they have been around for a while, suggesting that they may be tricky to fix, or at least requires a time investment from someone knowledgable. We have a few type system issues, a scope issue with inherit, a test case that breaks the pike stack and broken dumped file system. - Valgrind currently takes issue with a few of the tests. Check if these are real and fix them. - We have a few documentation issues reported by the autodoc extractor. These should be fixed. - Test that exported source and exported builds compile/installs/work. - Set up Xenofarm to build Pike 8. - Check if there are obvious performance regressions from 7.8, and address them if that appears to be easy. - And everyones favorite; Write a changelog. For the next version of Pike we want to be more explicit about supported operating systems. Linux, Solaris, MacOS, Windows and, if Marcus supports it, AmigaOS. - Remove configure and transition to a profile based system where a pike script generates header files. - Remove the compat system, as it creates a lot of maintenance overhead, ugly code and is of dubious value in practice. - Consider removing the less used C modules to cut down on dependenices and compilation time. DVB, Mird, spider and PDF were mentioned as examples. - Remove the Pike security system. This is not maintained and would simplify the code. - Remove the bundle system. All the bundle dependencies are now available as packages and most are already installed by default. - Make support for bignums mandatory, to remove all ifdef bignum code. - Remove support for old systems (e.g. outdated code in port.c) - Remove short svalue support. - Remove Fd_ref from Stdio.File, currently implemented under STDIO_DIRECT_FD define. - Implement typed constants. - Implement "operator" as an alternative syntax for "`". - Replace block alloc with a single (and better) implementation. - Remove local calendar locale configuration support. - Split mega apply into a pike and a C version to speed up calls between pike functions. - Remove the mark stack. - Renumber the types so that PIKE_T_INT becomes 0. Any item that makes the release of 8.0 easier and faster should be done there rather than later.

6 27

Pike on Hurd
by Magnus Holmgren 07 Jun '13

07 Jun '13

Trying to get Pike (7.8.700 still) to compile on Debian GNU/Hurd (which was officially released(!) on May 23, for some value of "released"), I found three issues: 1. PATH_MAX used as the size of the buffer passed to realpath() in system.c. pathnames can be arbirarily long on Hurd, so one should in this instance pass NULL to realpath and let it allocate the returned string itself. 2. mach/message.h, which defines mach_msg_type_number_t, is not included by mach/task_info.h (or either of the other two .h files); we have to include it ourselves directly. 3. The GTK2 module uses a couple of Xlib functions without explicitly linking with -lX11, instead relying on the GTK libs to pull it in. This practice is discouraged/deprecated, but apparently still works with the toolchains on most of the architectures; I don't know why Debian GNU/Hurd is different in this regard. I've created a patch that addresses these issues, but I'm not sure if it integrates in the most clean way. It's also untested, because pike dies right away when run to generate the documentation (I've: uncommented the several fprintf calls in object.c): Need a new master object... Builtin_constants: 0x871ae3c Cannot load master object yet! /home/holmgren/pike7.8-7.8.700/src/object.c:695: Fatal error: Couldn't load master object. No stack - no backtrace. Backtrace from gdb: #9 0x08144d47 in debug_fatal (fmt=fmt@entry=0x84b6eb7 "Couldn't load master object.\n") at /home/holmgren/pike7.8-7.8.700/src/error.c:654 #10 0x08186ce9 in debug_master () at /home/holmgren/pike7.8-7.8.700/src/object.c:695 #11 0x083beca9 in resolve_syms () at /Users/hww3/pike- build/src/post_modules/GSSAPI/gssapi.cmod:434 #12 0x083bf12d in get_dd_oid (gss_oid=0x182d8c0) at /Users/hww3/pike- build/src/post_modules/GSSAPI/gssapi.cmod:351 #13 0x083ca9c8 in pike_module_GSSAPI_init () at /Users/hww3/pike- build/src/post_modules/GSSAPI/gssapi.cmod:4450 #14 0x082106d7 in init_modules () at /home/holmgren/pike7.8-7.8.700/src/module.c:424 #15 0x0817b7a5 in init_pike_runtime (exit_cb=0x80e6f00 <exit@plt>) at /home/holmgren/pike7.8-7.8.700/src/pike_embed.c:418 #16 0x080e8f1d in main (argc=4, argv=0x3dffd68) at /home/holmgren/pike7.8-7.8.700/src/main.c:610 It seems that _static_modules isn't set yet. Any idea why? Or rather, why is debug_master() called while initializing the static modules? Oh, now I know! The problem is of course that the modules aren't being linked dynamically at all. That's probably the reason behind issue #3, too. I guess there's been some code rot because nobody ever links the modules statically. You might want to look into why static modules don't work - but probably not... -- Magnus Holmgren holmgren(a)debian.org Debian Developer

3 4

FYI/RFC: Variant functions in Pike 7.9
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 28 May '13

28 May '13

FYI: The support for variant function (aka polymorphic overloading) has now reached a semi-useable state in Pike 7.9: | Pike v7.9 release 5 running Hilfe v3.5 (Incremental Pike Frontend) | > class foo { | >> variant int bar(int a) { return a*2; } | >> variant string bar(string s) { return "FOO" + s + "FOO"; } | >> variant string bar() { return "FOO"; } | >> } | > typeof(foo()->bar); | (1) Result: function( : string) | function(int : int) | function(string : string) | > foo()->bar(17); | (2) Result: 34 | > foo()->bar("BAR"); | (3) Result: "FOOBARFOO" | > foo()->bar(); | (4) Result: "FOO" | > foo()->bar(1.2); | Compiler Error: 1: Bad argument 1 to bar. | Compiler Error: 1: Expected: string | int. | Compiler Error: 1: Got : float. | > foo()->bar((mixed)1.2); | Invalid arguments to bar()! | HilfeInput:1: HilfeInput()->foo()->bar(1.2) | HilfeInput:1: HilfeInput()->___HilfeWrapper() I would appreciate feedback especially regarding the expected semantics for: * When the variants have different modifiers (protected, private, etc). * When there's a function without the variant keyword. * When the types for the variants aren't disjunct. * When overriding X from an inherit with a variant function. - A non-variant function. - A variant function with a new definition with the same type. - A variant function with a new definition with a different type. * Should the previous definition be accessible in any of the above cases, or only if there's an explicit trampoline? * Multiple inherits of variant functions. - With the same types. - With different types. I've probably forgotten or not thought of some cases, please mention the expected semantics for these as well. /grubba

4 4

Fwd: Bug#708366: pike7.8: FTBFS due to conflicting REG_* definitions
by Magnus Holmgren 26 May '13

26 May '13

OK, so now all of REG_EAX, REG_EBX and so on are defined on Linux, or rather, in the newest eglibc. Do you prefer renaming the enum items or #undef-ing all of them? ---------- Forwarded message ---------- Subject: Bug#708366: pike7.8: FTBFS due to conflicting REG_* definitions Date: onsdagen den 15 maj 2013 From: Colin Watson <cjwatson(a)ubuntu.com> To: submit(a)bugs.debian.org Package: pike7.8 Version: 7.8.700-2 Severity: serious User: ubuntu-devel(a)lists.ubuntu.com Usertags: origin-ubuntu saucy pike7.8 fails to build in unstable as follows: Compiling pikecode.c In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0: /«PKGBUILDDIR»/src/code/ia32.c:22:16: error: redeclaration of enumerator 'REG_EAX' In file included from /usr/include/signal.h:360:0, from /usr/include/i386-linux-gnu/sys/param.h:28, from /«PKGBUILDDIR»/src/pike_macros.h:14, from /«PKGBUILDDIR»/src/program.h:12, from /«PKGBUILDDIR»/src/pikecode.c:15: /usr/include/i386-linux-gnu/sys/ucontext.h:180:3: note: previous definition of 'REG_EAX' was here In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0: /«PKGBUILDDIR»/src/code/ia32.c:22:29: error: redeclaration of enumerator 'REG_EBX' In file included from /usr/include/signal.h:360:0, from /usr/include/i386-linux-gnu/sys/param.h:28, from /«PKGBUILDDIR»/src/pike_macros.h:14, from /«PKGBUILDDIR»/src/program.h:12, from /«PKGBUILDDIR»/src/pikecode.c:15: /usr/include/i386-linux-gnu/sys/ucontext.h:174:3: note: previous definition of 'REG_EBX' was here *snip* It looks painful to reliably avoid the enumeration values in <sys/ucontext.h>. I suggest simply renaming Pike's enumeration values. Thanks, -- Colin Watson [cjwatson(a)ubuntu.com] ------------------------------------------------------- -- Magnus Holmgren holmgren(a)debian.org Debian Developer

2 2

callback support for encoding JSON
by Martin Bähr 24 May '13

24 May '13

hi, the JSON module can only encode objects if they provide an encode_json function. i find this a bit limiting because it is hardly possible to add encode_json to all classes that would need it. better would be to allow the caller of JSON.encode provide a callback for objects that the module can't handle by itself. it seems to me the simplest would be to add an argument to JSON.encode to allow passing a function. and then call that function of the object has none of its own. i am unfamiliar with CMODs but i think in src/post_modules/JSON/json.cmod i need to add the function to the encode_context and then call it in the PIKE_T_OBJECT case. also what i am wondering is, should i store the whole svalue for the function or just the functionpointer itself? (is that u.efun->function?) greetings, martin.

5 19

Segfaults and module dumping failures starting in acab7b82dc
by H. William Welliver III 23 May '13

23 May '13

I've noticed that installs of 7.9 after commit acab7b82dc have started generating a large number of module dumping failures. Also, I have code that segfaults on startup starting with the same commit. The code is somewhat complicated, so I've not been able to boil it down to a simple test (yet). I'm not sure the gdb backtrace will be of much help, but I'll include it here. Any suggestions? Bill Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000180 [Switching to process 19605 thread 0x1803] 0x000000010017f8a5 in insert_opcode1 () (gdb) bt #0 0x000000010017f8a5 in insert_opcode1 () #1 0x0000000100067fd7 in do_docode2 () #2 0x000000010006be4f in do_docode2 () #3 0x00000001000710a2 in do_cond_jump () #4 0x0000000100071002 in do_cond_jump () #5 0x000000010006ecae in do_docode2 () #6 0x000000010006854d in do_docode2 () #7 0x0000000100070a24 in do_code_block () #8 0x000000010016331a in dooptcode () #9 0x000000010000b0eb in yyparse () #10 0x0000000100107a76 in run_pass2 () #11 0x000000010010b5da in f_compilation_compile () #12 0x0000000100018235 in low_mega_apply () #13 0x0000000100019684 in mega_apply () #14 0x00000001000efe76 in f_compilation_env_compile () #15 0x0000000100018235 in low_mega_apply () #16 0x0000000100019684 in mega_apply () #17 0x0000000101181f6e in ?? () #18 0x000000010000f736 in catching_eval_instruction () #19 0x000000010001caeb in inter_return_opcode_F_CATCH () #20 0x000000010118b425 in ?? () #21 0x000000010001969f in mega_apply () #22 0x00000001000dca1d in object_index_no_free () #23 0x00000001007e2dcc in ?? () #24 0x000000010001969f in mega_apply () #25 0x00000001000dca1d in object_index_no_free () #26 0x00000001000eb3bc in f_index () #27 0x00000001001590cf in index_node () #28 0x000000010000a561 in yyparse () #29 0x000000010010b4f1 in f_compilation_compile () #30 0x0000000100018235 in low_mega_apply () #31 0x0000000100019684 in mega_apply () #32 0x00000001000efe76 in f_compilation_env_compile () #33 0x0000000100018235 in low_mega_apply () #34 0x0000000100019684 in mega_apply () #35 0x0000000101181f6e in ?? () #36 0x000000010000f736 in catching_eval_instruction () #37 0x000000010001caeb in inter_return_opcode_F_CATCH () #38 0x000000010118b425 in ?? () #39 0x000000010001969f in mega_apply () #40 0x00000001000dca1d in object_index_no_free () #41 0x00000001007e2dcc in ?? () #42 0x000000010001969f in mega_apply () #43 0x00000001000dca1d in object_index_no_free () #44 0x00000001000eb3bc in f_index () #45 0x00000001001590cf in index_node () #46 0x000000010000a561 in yyparse () #47 0x000000010010b4f1 in f_compilation_compile () #48 0x0000000100018235 in low_mega_apply () #49 0x0000000100019684 in mega_apply () #50 0x00000001000efe76 in f_compilation_env_compile () #51 0x0000000100018235 in low_mega_apply () #52 0x0000000100019684 in mega_apply () #53 0x0000000101181f6e in ?? () #54 0x000000010000f736 in catching_eval_instruction () #55 0x000000010001caeb in inter_return_opcode_F_CATCH () #56 0x000000010118b425 in ?? () #57 0x000000010001969f in mega_apply () #58 0x00000001000dca1d in object_index_no_free () #59 0x00000001007e2dcc in ?? () #60 0x000000010001969f in mega_apply () #61 0x00000001000dca1d in object_index_no_free () #62 0x00000001000eb3bc in f_index () #63 0x00000001001590cf in index_node () #64 0x000000010000a561 in yyparse () #65 0x000000010010b4f1 in f_compilation_compile () #66 0x0000000100018235 in low_mega_apply () #67 0x0000000100019684 in mega_apply () #68 0x00000001000efe76 in f_compilation_env_compile () #69 0x0000000100018235 in low_mega_apply () #70 0x0000000100019684 in mega_apply () #71 0x0000000101181f6e in ?? () #72 0x000000010000f736 in catching_eval_instruction () #73 0x000000010001caeb in inter_return_opcode_F_CATCH () #74 0x000000010118b425 in ?? () #75 0x000000010001969f in mega_apply () #76 0x00000001000e4517 in o_cast () #77 0x00000001000e4c2c in f_cast () #78 0x00000001049abfe1 in ?? () #79 0x000000010001969f in mega_apply () #80 0x00000001000d5db8 in call_pike_initializers () #81 0x00000001000d992c in debug_clone_object () #82 0x00000001000182fc in low_mega_apply () #83 0x000000010001bda4 in jump_opcode_F_CALL_FUNCTION () #84 0x0000000101e3f4d4 in ?? () #85 0x000000010000f736 in catching_eval_instruction () #86 0x000000010001caeb in inter_return_opcode_F_CATCH () #87 0x0000000101e3f179 in ?? () #88 0x000000010001969f in mega_apply () #89 0x000000010012e5a0 in new_thread_func () #90 0x00007fff8d1af742 in _pthread_start () #91 0x00007fff8d19c181 in thread_start ()

1 0

segfault when building pike 7.8 on olpc/fedora 18
by Martin Bähr 20 May '13

20 May '13

hi, i am getting a strange segfault after building pike: pike itself seems to build but it doesn't run. when i remove shuffler, then the build completes, but the same error comes back when i try make install. #### Making dynamic: post_modules/Shuffler [29/1915] /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/local/users/mbaehr/home/src/Pike-v7.8.700/bui ld/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i686/master.pike /local/users/mbaehr/home/src/Pi ke-v7.8.700/src/post_modules/Shuffler/make_sources.pike /local/users/mbaehr/home/src/Pike-v7.8.70 0/src/post_modules/Shuffler sources.h sources_to_compile /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:42: Error in constant definition. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:187: Failed to index module Files with 'Stat'. (Module doesn't exist?) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:368: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:368: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:376: No inherit or surrounding class Pike_0_5_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:411: No inherit or surrounding class Pike_0_5_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:438: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:438: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:649: No inherit or surrounding class Pike_0_6_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:673: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:673: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:712: No inherit or surrounding class Pike_7_0_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:736: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:736: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:806: No inherit or surrounding class Pike_7_2_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:830: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:830: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:864: No inherit or surrounding class Pike_7_4_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:881: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:881: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:1490: Error in constant definition. make[4]: *** [override] Segmentation fault make[3]: *** [Shuffler] Error 1 make[2]: *** [post_module_objects] Error 1 make[1]: *** [_make_in_builddir] Error 2 make: *** [compile] Error 2 greetings, martin. -- eKita - the online platform for your entire academic life hackerspace beijing - http://societyserver.org/hackerspace-beijing/ -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net foresight developer realss.com foresightlinux.org unix sysadmin trainer developer societyserver.org Martin Bähr working in china http://societyserver.org/mbaehr/

2 4

Strict types
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 19 May '13

19 May '13

I don't think a == comparison between a string and a string(0..255) should generate a warning. Is that really useful?

1 0

JPEG transforms
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 08 May '13

08 May '13

I want to ask about the change to have EXIF data modify the JPEG decoding. I can see why it would be desired to have a method that does it, but why would that be the default behavior? Are there any other applications/libs that does this by default?

3 2

Jump to page:

2026

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