Pike-devel January 2014

pike-devel@lists.lysator.liu.se

5 participants
6 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

pike 7.8 alpha
by H. William Welliver III 24 Jan '14

24 Jan '14

I've uploaded a tentative "alpha" release, 7.8.808. Please feel free to download and comment. If everything looks good, I'll promote it to beta in a week or so (or will prepare a new alpha if things don't look so good). http://pike.lysator.liu.se/download/pub/pike/alpha/7.8.808/ Best, Bill

4 6

do crash pike
by Martin Bähr 15 Jan '14

15 Jan '14

hi, in pike 7.6 the following leads to a clean error: void do(){}; mixed ___HilfeWrapper() { return do; } crash.pike:1:do is a reserved word. crash.pike:2:do is a reserved word. crash.pike:2:syntax error, unexpected ';' Pike: Failed to compile script: Compilation failed. in 7.8 or 7.9 it leads to a fatal crash: pike79 crash.pike crash.pike:1:do is a reserved word. /local/users/mbaehr/src/pike/src/pike_types.c:677: Fatal error: Type mark stack underflow Backtrace at time of fatal: -:1: PikeCompiler("", UNDEFINED, -1, -1, target, UNDEFINED)->compile() -:1: DefaultCompilerEnvironment->compile(PikeCompiler("", UNDEFINED, -1, -1, target, UNDEFINED)) /usr/local/pike/7.9.5/lib/master.pike:1172: compile_string("void do(){}\nmixed ___HilfeWrapper() { return do; }\n","/local/users/mbaehr /home/src/pike/crash.pike",UNDEFINED,/local/users/mbaehr/home/src/pike/crash,0,UNDEFINED) /usr/local/pike/7.9.5/lib/master.pike:1896: master()->low_findprog("/local/users/mbaehr/home/src/pike/crash",".pike",UNDEFINED,UNDEFINE D) /usr/local/pike/7.9.5/lib/master.pike:2011: master()->findprog("/local/users/mbaehr/home/src/pike/crash",".pike",UNDEFINED,UNDEFINED) /usr/local/pike/7.9.5/lib/master.pike:2050: master()->low_cast_to_program("/local/users/mbaehr/home/src/pike/crash","/usr/local/pike/7. 9.5/lib/master.pike",UNDEFINED,UNDEFINED) /usr/local/pike/7.9.5/lib/master.pike:2084: master()->cast_to_program("/local/users/mbaehr/home/src/pike/crash.pike","/usr/local/pike/7 .9.5/lib/master.pike",UNDEFINED) fish: Job 2, “pike79 crash.pike ” terminated by signal SIGABRT (Abort) this works in different variations. void do() { mixed bar = ""; } or void do() {} mixed bar() { return ""; } trigger the same error, whereas void do(){} void do(){ write("bar"); } mixed do(){ return 1; } all work correctly greetings, martin.

2 1

Re: pike.lysator access
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 03 Jan '14

03 Jan '14

> Hi Grubba, Hi Bill. > Thanks for looking into this for me. I just tried to log in to > pike.lysator.liu.se and was prompted for a password. I did verify > that both ida and git accounts work properly with the keys I'm > using. Can you take a look to make sure things are okay? After some investigation, I found that the problem was that sshd didn't like the password entry for your account. Try now. > Bill /Grubba

1 0

pike.lysator access
by H. William Welliver III 02 Jan '14

02 Jan '14

I've got a pike 7.8 alpha prepared, but I'm having trouble logging in to pike.lysator.liu.se. Can someone with access verify my account (bill) and key? I'm still able to access the server at liu, so if that key can be used, that'd be helpful. Bill

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 January 2014