Pike-devel March 2004

pike-devel@lists.lysator.liu.se

9 participants
48 discussions

nettle + xenofarm
by Mirar ＠ Pike developers forum 07 Mar '04

07 Mar '04

Excellent test. Now to the next problem. Almost all xenofarm building computers doesn't have nettle installed, which makes their result worthless. Should someone mail the computer owners urging for a nettle install, or should xenofarm include nettle?

3 3

Pike on FreeBSD Alpha
by Xavier Beaudouin 04 Mar '04

04 Mar '04

Hello, Pike 7.2 and 7.4 are broken on FreeBSD 5.x Alpha Please have a look at these logs http://bento.freebsd.org/errorlogs/alpha-5-latest/pike72-7.2.492_2.log http://bento.freebsd.org/errorlogs/alpha-5-latest/pike74-7.4.43.log And tell me how I can fix this obvious errors... /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

3 3

SSL in 7.5 is broken?
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 04 Mar '04

04 Mar '04

(Hm. What a verbose way of saying "Is the source code available to someone who might feel inclined to help you?". :-)

5 10

SSL in 7.5 is broken?
by Alexander Demenshin 03 Mar '04

03 Mar '04

Hi, Just attempted to run my test app (simple SSL server) on 7.5, but it doesn't work well: aldem@asv:~> openssl s_client -connect 127.0.0.1:8443 -state -ssl3 CONNECTED(00000003) SSL_connect:before/connect initialization SSL_connect:SSLv3 write client hello A SSL_connect:SSLv3 read server hello A depth=0 /C=DE/ST=Thueringen/L=Ilmenau/O=TU Ilmenau/OU=PMI/CN=demo server verify error:num=18:self signed certificate verify return:1 depth=0 /C=DE/ST=Thueringen/L=Ilmenau/O=TU Ilmenau/OU=PMI/CN=demo server verify error:num=10:certificate has expired notAfter=May 30 05:36:59 1996 GMT verify return:1 depth=0 /C=DE/ST=Thueringen/L=Ilmenau/O=TU Ilmenau/OU=PMI/CN=demo server notAfter=May 30 05:36:59 1996 GMT verify return:1 SSL_connect:SSLv3 read server certificate A SSL_connect:SSLv3 read server done A SSL_connect:SSLv3 write client key exchange A SSL_connect:SSLv3 write change cipher spec A SSL_connect:SSLv3 write finished A SSL_connect:SSLv3 flush data SSL_connect:failed in SSLv3 read finished A 30801:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:529: So it breaks somewhere... Unfortunately, I wasn't following recent changes in SSL code (there are many) - so - is it just unsafe now or something which isn't normal? In the app accept_callback is called - but nothing more happens (connection is closed silently, somewhere deep inside, even cb_close isn't called). Any ideas? :) (Yes, is 7.4 same apps works perfectly :) Regards, /Al

2 1

verify failure (not catched by xenofarm testsuite)
by Alexander Demenshin 03 Mar '04

03 Mar '04

Hi, I got the following: /home/aldem/src/Pike/Pike7.5-20040229-221338/src/testsuite.in:10137: Test 10355 (shift 2) (CRNL) produced warning. 0: Decode failed: Got unfinished program <18> after decode: program(/home/aldem/src/Pike/Pike7.5-20040229-221338/src/test-install/pike/7.5.19/lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Request.pike) Is it fatal? Or I can safely ignore it? Regards, /Al

2 3

valgrinding Pike - some problems
by Alexander Demenshin 02 Mar '04

02 Mar '04

Hi, Just attempted to valgrind recent version (from CVS), immediately got thousands of errors like this: ==7875== Conditional jump or move depends on uninitialised value(s) ==7875== at 0x81B5AF7: debug_check_node_hash (las.c:830) ==7875== by 0x81506F1: optimize_binary (operators.c:1712) ==7875== by 0x81C8A04: optimize (treeopt.h:3289) ==7875== by 0x81CCCF3: optimize_node (las.c:5363) Where is the catch? It seems that entire structure is initialized correctly upon allocation (there is a call to MEMSET)... What makes me curious, though - is - where alloc_node_s() is defined? Grepping all files in src/ gives single match - call to this function, object file symbol table says that alloc_node_s() is defined in las.c, but... Regards, /Al

4 13

pike in latvia
by Martin Bähr 01 Mar '04

01 Mar '04

hi, first of all, thanks for the invitations i have received, i hope to be able to follow them some time. a few days ago i arrived in latvia and i am already spending my time here helping out with all sorts of pike problems. this evening i'd like to invite everybody in or near riga who is interrested in pike to get together for an informal discussion on how we can make the best use of my time here in latvia, to teach and present pike. we will be planning tutorials and presentations according to need and interest. there are no requirements to participate (just interest in pike :-) the meeting location is in the offices of interneta pasaule Kr Barona 24/26 (3rd floor) (near vermanes parks) in riga suggested meeting time is around 7pm. looking forward to seeing you there. greetings, martin. ps: please pass on this message as you see fit. -- looking for a job doing pike programming, sTeam/caudium/pike/roxen training, sTeam/caudium/roxen and/or unix system administration anywhere in the world. -- pike programmer travelling and working in europe (latvia) open-steam.org unix system- bahai.or.at iaeste.(tuwien.ac|or).at administrator (stuts|black.linux-m68k).org is.schon.org Martin Bähr http://www.iaeste.or.at/~mbaehr/

1 1

Access to default `->() in C modules
by Alexander Demenshin 01 Mar '04

01 Mar '04

Hi, I would to implement [kind of] properties in C module, so it will be possible to access some variables like obj->prop. I tried map_variable() first, but it doesn't work well - it's value can be changed outside of object (may be there is an attribute to disable this?), and - it cannot be (safely) extracted with get_all_args() - since size of Pike's int/float is not necessary same as size of C int/float (and I don't want to use Pike types everywhere in C data structures). So... The logical way is to implement `->() function, but I don't know how to do this in C (not exactly). In Pike, I can use something like ::`->() to call predefined (original) indexing operator, so what should I do in C? Or, more precise, how? Regards, /Al

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 March 2004