Pike-devel November 2009

pike-devel@lists.lysator.liu.se

5 participants
10 discussions

pcvs2git.pike
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 14 Mar '10

14 Mar '10

I just tried converting Roxen 2.4: Stage Memory use Commits --------------------------------------- Import 339 MB ~17000 Raking 359 MB ~17000 Verify 361 MB ~17000 Merging 662 MB 11886 Graphing 803 MB 10897 Generate 803 MB 10897 I believe that the memory use can be reduced by using more custom datatypes (currently there are a lot of mappings generated in the merging and graphing stages). Another way to reduce the memory use is to partition the graphs in the time axis.

5 58

mysql charset issue
by Arne Goedeke 11 Jan '10

11 Jan '10

I observed that the Mysql module doesnt seem to reset the connection charset after a reconnect. This occurs when using something like set_charset("unicode") which triggers a "SET NAMES UTF-8". However, in case the connection is lost and the sql object reconnects automatically, it does not send the SET NAMES again. The data then comes back in latin1 and the Sql modules tries to decode them in fetch_rows(). I am using a recent pike 7.8.365, etc. Arne

3 11

eureka reinstall
by Peter Bortas ＠ Pike developers forum 07 Jan '10

07 Jan '10

Some time next week I'll upgrade eureka from Solaris Express snv_81 to whatever the latest stable OpenSolaris release is. There is no straight forward upgrade path from SXCE to OpenSolaris, so the machine will be reinstalled and the data restored from backup. That means there will be some substancial downtime for people using services on eureka. More details later.

4 13

More rtldebug to get better info when gc_mark problems happen.
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 14 Dec '09

14 Dec '09

Um, the latest commit to Makefile (by mast) was a mistake, no?

4 4

patch for string_builder_vsprintf
by Arne Goedeke 30 Nov '09

30 Nov '09

Hello, I noticed that only %f is supported in string_builder_vsprintf(). I would like to use something else in JSON2, so it would be nice if someone could review this and maybe commit. arne diff --git a/src/stralloc.c b/src/stralloc.c index eb60b8b..e75d45b 100644 --- a/src/stralloc.c +++ b/src/stralloc.c @@ -2945,13 +2945,17 @@ PMOD_EXPORT void string_builder_vsprintf(struct string_builder *s, flags, min_width, precision); break; - /* FIMXE: TODO: Doubles (ie 'a', 'e', 'E', 'g', 'G'). */ - /* %f used in modules/Image/colors.c. */ + case 'a': + case 'g': + case 'G': + case 'e': + case 'E': case 'f': { double val = va_arg(args, double); size_t bytes; + char nfmt[] = { '%', *(fmt-1), 0 }; if (PIKE_ISNAN(val)) { /* NaN */ @@ -2974,9 +2978,9 @@ PMOD_EXPORT void string_builder_vsprintf(struct string_builder *s, break; } /* FIXME: Field lengths and precision. */ - if ((bytes = SNPRINTF(NULL, 0, "%f", val))) { + if ((bytes = SNPRINTF(NULL, 0, nfmt, val))) { p_wchar0 *p = string_builder_allocate(s, bytes, 0); - size_t check = SNPRINTF((char*)p, bytes+1, "%f", val); + size_t check = SNPRINTF((char*)p, bytes+1, nfmt, val); if (check != bytes) { Pike_fatal("string_builder_vsprintf(): snprintf(%f) is not " "trustworthy: %"PRINTSIZET"u != %"PRINTSIZET"u\n",

3 2

The OOB working test
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 28 Nov '09

28 Nov '09

I noticed that the OOB check fails with TIMEOUT in 7.8 on my linux box. It produces SEMIWORKING in 7.6, so something is different in the configure script, although the test itself is identical. The log doesn't say much. Here's from 7.8: configure:70034: checking how well OOB handling works configure:70366: /home/mast/Pike/no-changes-7.8/build/linux-x86_64/smartlink gcc -o conftest -g -O3 -pipe -ggdb3 -m64 -I/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/include -I/usr/local/include -I/home/mast/Pike/no-changes-7.8/src -I/home/mast/Pike/no-changes-7.8/build/linux-x86_64 -L/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/lib64 -L/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/lib/64 -L/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/lib/. -L/usr/local/lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4 -R/usr/lib/gcc/x86_64-linux-gnu/4.4 conftest.c -ldl -lrt -lnsl -lm -lpthread -lcrypt >&5 conftest.c: In function 'my_socketpair': conftest.c:362: warning: incompatible implicit declaration of built-in function 'memset' conftest.c: In function 'ping': conftest.c:527: warning: incompatible implicit declaration of built-in function 'exit' conftest.c:535: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pong': conftest.c:552: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pang': conftest.c:570: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'main': conftest.c:591: warning: incompatible implicit declaration of built-in function 'exit' configure:70366: $? = 0 configure:70366: ./conftest my_socketpair: succeeded configure:70366: $? = 0 configure:70381: result: TIMEOUT Compared to 7.6: configure:50000: checking how well OOB handling works configure:50342: /home/mast/Pike/frozen/build/linux-x86_64/smartlink gcc -o conftest -g -O2 -pipe -Wa,--execstack -I/home/mast/Pike/frozen/build/linux-x86_64/bundles/include -I/usr/local/include -I/home/mast/Pike/frozen/src -I/home/mast/Pike/frozen/build/linux-x86_64 -L/home/mast/Pike/frozen/build/linux-x86_64/bundles/lib -z execstack -R/usr/local/lib -L/usr/local/lib -R/usr/X11R6/lib -L/usr/X11R6/lib -R/usr/lib/gcc/x86_64-linux-gnu/4.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.4 conftest.c -ldl -lrt -lnsl -lm -lpthread -lcrypt >&5 conftest.c: In function 'my_socketpair': conftest.c:333: warning: incompatible implicit declaration of built-in function 'memset' conftest.c: In function 'ping': conftest.c:498: warning: incompatible implicit declaration of built-in function 'exit' conftest.c:506: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pong': conftest.c:523: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pang': conftest.c:541: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'main': conftest.c:562: warning: incompatible implicit declaration of built-in function 'exit' configure:50345: $? = 0 configure:50351: ./conftest my_socketpair: succeeded configure:50354: $? = 0 configure:50375: result: SEMIWORKING I've tried changing the compiler flags to match 7.6 (-O2 instead of -O3 etc), but it doesn't change anything. What could the problem be?

2 2

Protocols.DNS.server
by Tobias S. Josefowitz 28 Nov '09

28 Nov '09

I've added multi-port-functionality and the ability to reply to DNS queries asynchronously to Protocols.DNS.server. A diff file is attached. Tobias

1 0

do_async_method_url ignoring content-type
by Arne Goedeke 14 Nov '09

14 Nov '09

do_async_method_url overrides the content-type given in extra headers. Its possible to work around it by using "Content-Type" instead of "content-type". This is relevant at least in the XMLRPC module, not sure if anybody noticed. here is a patch arne diff --git a/lib/modules/Protocols.pmod/HTTP.pmod/Session.pike b/lib/modules/Protocols.pmod/HTTP.pmod/Session.pike index 5b82fc9..b7e2e74 100644 --- a/lib/modules/Protocols.pmod/HTTP.pmod/Session.pike +++ b/lib/modules/Protocols.pmod/HTTP.pmod/Session.pike @@ -874,8 +874,8 @@ Request async_do_method_url(string method, if (method=="POST") extra_headers= - (extra_headers||([]))+ - (["content-type":"application/x-www-form-urlencoded"]); + (["content-type":"application/x-www-form-urlencoded"])+ + (extra_headers||([])); p->do_async(p->prepare_method(method,url,query_variables, extra_headers,data));

2 8

hilfe bug
by Arne Goedeke 11 Nov '09

11 Nov '09

2 1

Pike 7.8.360 alpha
by Peter Bortas ＠ Pike developers forum 01 Nov '09

01 Nov '09

New build that I really haven't tried at all, but to get things started: http://pike.ida.liu.se/download/pub/pike/beta/7.8.360/ No windows build avilable. Changes since Pike 7.8.352 (third 7.8 release): ---------------------------------------------------------------------- Bug fixes --------- o Fixed segfault in combine_path_nt on windows when the first char of an appended path is wide. o Fixed a problem in "pike -x module" that prevented auto tools from running in the correct directory. o Fixed memory leak on out of memory in Mysql.fetch_json_result(). o Fixed locking problem in Mysql. o Fixed NULL-deref for compilation errors in range expressions. o Fixes a segfault occuring if exit() is used from a thread when cleanup-on-exit is compiled in. Building and installing ----------------------- o Fixed som library searchpath issues. o Some potential fixes for --enable-pikelib mode on platforms had problems with the final linking.

2 2

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 November 2009