Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Threads under win2k
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 27 May '04

27 May '04

Using Pike 7.5.17 compiled by Peter Bortas, I got the following error: \home\peter\hack\Pike\7.5\src\threads.c:65: Fatal error: \home\peter\hack\Pike\7.5\src\threads.c:182: WaitForSingleObject((*(&c->lock)), 0xFFFFFFFF) == ((((DWORD )0x00000000L) ) + 0 ) Unexpected error from thread function: 6 Backtrace at time of fatal: Is that a known bug? My code starts a lot of threads (about 20 simultaniously running) which scans directories for their permissions.

2 2

Compiler bug
by David Gourdelier 27 May '04

27 May '04

Hi, Here is a new bug of Pike 7.6(.9) on FreeBSD (5.2.1): $ cat segfault.pike void set_expire_hook(function exphook, void|mixed ...fargs, string|object id) { } int main() { } $ pike segfault.pike segfault.pike:1:Can't define more arguments after ... /home/david/Pike/7.6/src/pike_types.c:717: Fatal error: Unexpected type on stack: 255 (expected 0) Backtrace at time of fatal: /usr/local/pike/7.6.9/lib/master.pike:346: object(/usr/local/pike/7.6.9/lib/master.pike)->compile_string("void set_expire_hook(function exphook, void|mixed ...fargs, string|object id)\n{\n}\n\nint main()\n{\n}\n","/home/david/scripts/segfault.pike",0,/home/david/scripts/segfault,0) /usr/local/pike/7.6.9/lib/master.pike:813: object(/usr/local/pike/7.6.9/lib/master.pike)->low_findprog("/home/david/scripts/segfault",".pike",0,0) /usr/local/pike/7.6.9/lib/master.pike:907: object(/usr/local/pike/7.6.9/lib/master.pike)->findprog("/home/david/scripts/segfault",".pike",0,0) /usr/local/pike/7.6.9/lib/master.pike:943: object(/usr/local/pike/7.6.9/lib/master.pike)->low_cast_to_program("/home/david/scripts/segfault","/usr/local/pike/7.6.9/lib/master.pike",0,0) /usr/local/pike/7.6.9/lib/master.pike:977: object(/usr/local/pike/7.6.9/lib/master.pike)->cast_to_program("/home/david/scripts/segfault.pike","/usr/local/pike/7.6.9/lib/master.pike",0) Abort trap (core dumped) It's 100% reproductible. / David

2 2

Quoting in Standards.URI
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 26 May '04

26 May '04

Seems like Standards.URI do neither encoding nor decoding according to rfc 2396: Pike v7.7 release 3 running Hilfe v3.5 (Incremental Pike Frontend) > object uri = Standards.URI("http://foo/a%3Fb?c"); > uri->path; (1) Result: "/a%3Fb" > _Roxen.http_decode_string (uri->path); (2) Result: "/a?b" > uri->path = _; (3) Result: "/a?b" > (string) uri; (4) Result: "http://foo/a?b?c" Is it per design? I think it's pretty clear that it should handle this detail too. Unfortunately it's quite a problem to change that now since this class already is used extensively, and changes in quoting behavior is one of the most notorious compatibility problem generators. Someone got any idea about how common it is that calling code "works around" this by doing its own encoding and decoding?

4 8

Quoting in Standards.URI
by Johan Sch�n (Firefruit) ＠ Pike (-) developers forum 26 May '04

26 May '04

Python's urlparse module also doesn't unescape: http://docs.python.org/lib/module-urlparse.html

1 0

Quoting in Standards.URI
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 May '04

26 May '04

Another one might be Subverson URL:s, if support for filenames containing "/" is ever added (could be used on old MacOS). There didn't seem to be much incentive for doing this last time I checked though. :-)

1 0

Process.create_process in 7.6
by Bill Welliver 25 May '04

25 May '04

It appears that one can no longer pass a Stdio.Port() object as stdin to Process.create_process. We had been using this method to process FastCGI, but now with 7.6, it seems that passing a Stdio.Port in options->stdin throws an error. Does anyone know if this was an intentional change or whether there's a workaround? Bill

2 1

Bittorrent bugs
by Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum 25 May '04

25 May '04

How serious are these kind of errors? Got POLLERR on non-socket fd 173 (getsockopt errno=9) Got POLLERR on non-socket fd 197 (getsockopt errno=9) Got POLLERR on non-socket fd 99 (getsockopt errno=9) Got POLLERR on non-socket fd 92 (getsockopt errno=9) Got POLLERR on non-socket fd 174 (getsockopt errno=9) Got POLLERR on non-socket fd 70 (getsockopt errno=9) Got POLLERR on non-socket fd 58 (getsockopt errno=9) Got POLLERR on non-socket fd 159 (getsockopt errno=9)

2 3

Pike 7.2 not exported
by David Gourdelier 24 May '04

24 May '04

Hi, While trying the Pike 7.2 official releases at ftp://pike.ida.liu.se/pub/pike/all/7.2.239/ and ftp://pike.ida.liu.se/pub/pike/all/7.2.197/, I saw these versions are not exported: Compiling /home/david/archives/Pike-v7.2.197/src/queue.c ./precompile.sh precompile.pike >"/home/david/archives/Pike-v7.2.197/src/builtin.c" "/home/david/archives/Pike-v7.2.197/src/builtin.cmod" || { rm "/home/david/archives/Pike-v7.2.197/src/builtin.c"; exit 1; } precompile: /home/david/archives/Pike-v7.2.197/src/pike -DNOT_INSTALLED -m/home/david/archives/Pike-v7.2.197/src/master.pike ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=Q) ./precompile.sh: /home/david/archives/Pike-v7.2.197/src/pike: not found precompile: /home/david/archives/Pike-v7.2.197/src/tpike -DNOT_INSTALLED -m/home/david/archives/Pike-v7.2.197/src/master.pike ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=QQ) ./precompile.sh: /home/david/archives/Pike-v7.2.197/src/tpike: not found precompile: /home/david/archives/Pike-v7.2.197/src/test-pike ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=QQQ) ./precompile.sh: /home/david/archives/Pike-v7.2.197/src/test-pike: not found precompile: pike -DOLD ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=QQQQQQ) pike: not found blabla.... / David

1 0

Re: Suggestions to manual
by Martin Bähr 19 May '04

19 May '04

i am changing the list, as this is not relevant for pike users. On Tue, May 18, 2004 at 03:46:44PM +0200, Martin Stjernholm wrote: > > mixed m; > > typeof(m); > (1) Result: mixed > > typeof([int] m); > (2) Result: int > > Only the type is changed, hence a type cast. A normal cast like > (int) "1" changes the value, hence a value cast. the difference is than that [type] only changes the variable but not its value, whereas (type) changes both. in other languages (see the c and java examples), the term "type cast" is used to describe the first case where where both variable and value are changed. hence i think it is a bad idea to use a different definition in pike. coining new terms is fine, but chaning existing ones will lead to confusion. "variable cast" might work. greetings, martin.

5 5

Syslog fix
by David Gourdelier 19 May '04

19 May '04

Hi, I think there is a bug in system/syslog.c: if(i & (1<<0)) pri |= LOG_EMERG; if(i & (1<<1)) pri |= LOG_ALERT; if(i & (1<<2)) pri |= LOG_CRIT; if(i & (1<<3)) pri |= LOG_ERR; if(i & (1<<4)) pri |= LOG_WARNING; if(i & (1<<5)) pri |= LOG_NOTICE; if(i & (1<<6)) pri |= LOG_INFO; if(i & (1<<6)) pri |= LOG_DEBUG; Shouldn't it be 1<<7 instead of 1<<6 for the last line ? -- David Gourdelier

2 1

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