Pike-devel December 2009

pike-devel@lists.lysator.liu.se

4 participants
6 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 10 Jan '10

10 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 13 Dec '09

13 Dec '09

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

4 4

precompile problem on 7.8.352
by Bill Welliver 09 Dec '09

09 Dec '09

I've been trying to track down a problem when compiling CMODs on 7.8.352. It seems that there should be a define for DEFAULT_CMOD_STORAGE, but it never makes it to the output file. I verified that it's in the declarations at one point, but it seems to disappear or is ignored when it comes time to output. Any suggestions as to the problem? Bill

1 0

sscanf bug?
by Martin Bähr 03 Dec '09

03 Dec '09

hi, shouldn't those two examples be the same? > array_sscanf("124dsf134", "%d%s%3d"); (5) Result: ({ /* 2 elements */ 124, "dsf134" }) > array_sscanf("124dsf134", "%d%s%d"); (6) Result: ({ /* 3 elements */ 124, "dsf", 134 }) greetings, martin.

3 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 December 2009