Pike-devel June 2013

pike-devel@lists.lysator.liu.se

3 participants
5 discussions

debugger opcodes
by Bill Welliver 30 Oct '14

30 Oct '14

I noticed that folks have been working on code generation lately. Any chance it might be possible to implement some of the opcodes required to get debugging working (step, break, etc)? I seem to recall someone indicating it wasn't a terribly difficult task, but it's clearly beyond my understanding of the problem. Bill

4 6

Sql.pgsql behavior in case of errors
by aldem-pikedev＠aldem.net 21 Aug '14

21 Aug '14

Hi everyone, I am preparing to use Postgres in my app, found the following strange behavior: ---snip--- Sql.Sql db = Sql.Sql("pgsql://localhost", "test", "test", "test"); db->query("BEGIN"); db->query("INSERT INTO requests (SvTrId) VALUES ('lala')"); catch(db->query("INSERT INTO requests (SvTrId) VALUES ('lala')")); db->query("INSERT INTO requests (SvTrId) VALUES ('juju')"); db->query("ROLLBACK"); ---snip--- Database is opened, row with 'lala' is inserted, second query (obviously) fails as SvTrId is the primary key, but row with 'juju' is inserted *and* appears in the database - i.e. the transaction is *committed*! Studying source code show, that once error is encounter, session is reset, i.e. running transaction is rolled back, everything is closed, temporary tables are deleted and session variables are reset as well, and after that, the next statement(s) will be committed immediately, as there is no active transaction. In my opinion, this is not exactly correct behavior when statement fails, as session still may be needed (especially temporary tables, open cursors etc). Im some cases, this is perfectly normal when SQL statement fails, especially in SERIALIZED transaction isolation level, and it would be more practical to leave the decision as of what to do to the application. Yes, this is true that it is impossible to continue executing statements in failed transaction, but temporary tables etc. may still be needed. Also, silent reconnection is not a good idea too - when there are many transactional statements are executed - it would be nice to have an option to modify this behavior. Best regards, /Alexander

5 6

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

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 June 2013