Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

ssl communication stalls
by ee (erik eriksson) ＠ Pike (-) developers forum 27 Jan '07

27 Jan '07

(filed as bug #4304) Below is a test case for a problem where communication between two Pike processes over SSL stalls with Pike 7.6.86. To reproduce, run in two different terminals on the same computer. Start as 1) pike bug.pike server 2) pike bug.pike client Expected behaviour: a lot of communication back and forth between the two processes: ping?, pong!, etc Observed behaviour: 7.6.51: works as expected 7.6.66: works as expected 7.6.76: works as expected 7.6.86: communication stalled after first message sent 7.7: communication stalled after first message sent Some hints: - Reason for problem seems to be that the read callback is deregistred from the underlying file object. - A workaround for the problem seems to be to pass 1 as 3rd argument to macro RUN_MAYBE_BLOCKING in method direct_write in SSL.pmod/sslfile.pike instead of SSL_INTERNAL_READING, preventing the callback to be unregistred (possible side effects of workaround unknown) bug.pike: #!/usr/bin/env pike int i = 0; class Server { // from http.server string my_certificate = MIME.decode_base64( "MIIBxDCCAW4CAQAwDQYJKoZIhvcNAQEEBQAwbTELMAkGA1UEBhMCREUxEzARBgNV\n" "BAgTClRodWVyaW5nZW4xEDAOBgNVBAcTB0lsbWVuYXUxEzARBgNVBAoTClRVIEls\n" "bWVuYXUxDDAKBgNVBAsTA1BNSTEUMBIGA1UEAxMLZGVtbyBzZXJ2ZXIwHhcNOTYw\n" "NDMwMDUzNjU4WhcNOTYwNTMwMDUzNjU5WjBtMQswCQYDVQQGEwJERTETMBEGA1UE\n" "CBMKVGh1ZXJpbmdlbjEQMA4GA1UEBxMHSWxtZW5hdTETMBEGA1UEChMKVFUgSWxt\n" "ZW5hdTEMMAoGA1UECxMDUE1JMRQwEgYDVQQDEwtkZW1vIHNlcnZlcjBcMA0GCSqG\n" "SIb3DQEBAQUAA0sAMEgCQQDBB6T7bGJhRhRSpDESxk6FKh3iKKrpn4KcDtFM0W6s\n" "16QSPz6J0Z2a00lDxudwhJfQFkarJ2w44Gdl/8b+de37AgMBAAEwDQYJKoZIhvcN\n" "AQEEBQADQQB5O9VOLqt28vjLBuSP1De92uAiLURwg41idH8qXxmylD39UE/YtHnf\n" "bC6QS0pqetnZpQj1yEsjRTeVfuRfANGw\n"); string my_key = MIME.decode_base64( "MIIBOwIBAAJBAMEHpPtsYmFGFFKkMRLGToUqHeIoqumfgpwO0UzRbqzXpBI/PonR\n" "nZrTSUPG53CEl9AWRqsnbDjgZ2X/xv517fsCAwEAAQJBALzUbJmkQm1kL9dUVclH\n" "A2MTe15VaDTY3N0rRaZ/LmSXb3laiOgBnrFBCz+VRIi88go3wQ3PKLD8eQ5to+SB\n" "oWECIQDrmq//unoW1+/+D3JQMGC1KT4HJprhfxBsEoNrmyIhSwIhANG9c0bdpJse\n" "VJA0y6nxLeB9pyoGWNZrAB4636jTOigRAiBhLQlAqhJnT6N+H7LfnkSVFDCwVFz3\n" "eygz2yL3hCH8pwIhAKE6vEHuodmoYCMWorT5tGWM0hLpHCN/z3Btm38BGQSxAiAz\n" "jwsOclu4b+H8zopfzpAaoB8xMcbs0heN+GNNI0h/dQ==\n"); void create(Stdio.File file) { write("server: got connection\n"); SSL.context ctx = SSL.context(); ctx->random = Crypto.Random.random_string; ctx->rsa = Standards.PKCS.RSA.parse_private_key(my_key); ctx->certificates = ({ my_certificate }); SSL.sslfile f = SSL.sslfile(file, ctx, 0, 0); f->set_nonblocking(lambda(mixed id, string data) { write("server: (%d) got data <%s>, sending pong\n", i++, data); f->write("pong!"); }, lambda() { }, lambda() { write("server: close callback, exiting\n"); exit(-1); }, 0, 0, lambda() { write("server: handshake done, waiting for client to initiate\n"); }); } } class Client { void create(Stdio.File file) { SSL.context ctx = SSL.context(); ctx->random = Crypto.Random.random_string; SSL.sslfile f = SSL.sslfile(file, ctx, 1, 0); write("client: connected\n"); f->set_nonblocking(lambda(mixed id, string data) { write("client: (%d) got data <%s>, sending ping\n", i++, data); f->write("ping?"); }, lambda() { }, lambda() { write("client: close callback\n"); exit(-1); }, 0, 0, lambda() { write("client: handshake done, sending ping\n"); f->write("ping?"); }); } } void main(int argc, array argv) { int port = 12345; if (argc == 2 && argv[1] == "server") { Stdio.Port p = Stdio.Port(); p->bind(port, lambda() { Server(p->accept()); }); write("server: waiting for connection\n"); } else if (argc == 2 && argv[1] == "client") { write("client: connecting\n"); Stdio.File socket = Stdio.File(); socket->connect("localhost", port); Client(socket); } else { write("specify client or server\n"); exit(-1); } while (1) { Pike.DefaultBackend(); } }

2 2

pike crash
by ee (erik eriksson) ＠ Pike (-) developers forum 25 Jan '07

25 Jan '07

>the following program crashes my pike. tested on various installations >(debian or ubuntu, all running pike v 7.6.86). > >ee@sprint:~/tmp$ cat crash.pike >class S { > SSL.context s; > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } >} >void main(){} >ee@sprint:~/tmp$ pike crash.pike >Segmenteringsfel (core dumped) >ee@sprint:~/tmp$ cat nocrash.pike >class S { > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } > SSL.context s; >} >void main(){} >ee@sprint:~/tmp$ pike nocrash.pike >ee@sprint:~/tmp$ pike -v >Pike v7.6 release 86 Copyright %Gï¿½%@ 1994-2006 Link%Gï¿½%@ping University >Pike comes with ABSOLUTELY NO WARRANTY; This is free software and you are >welcome to redistribute it under certain conditions; Read the files >COPYING and COPYRIGHT in the Pike distribution for more details. filed as bug #4302 / ee (erik eriksson) Previous text: >15166557 2007-01-22 15:20 /29 lines/ ee (erik eriksson) >Recipients: Pike (-) erfarenhetsutbyte >Subject: pike crash >-------------------------------------------------------------------- >the following program crashes my pike. tested on various installations >(debian or ubuntu, all running pike v 7.6.86). > >ee@sprint:~/tmp$ cat crash.pike >class S { > SSL.context s; > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } >} >void main(){} >ee@sprint:~/tmp$ pike crash.pike >Segmenteringsfel (core dumped) >ee@sprint:~/tmp$ cat nocrash.pike >class S { > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } > SSL.context s; >} >void main(){} >ee@sprint:~/tmp$ pike nocrash.pike >ee@sprint:~/tmp$ pike -v >Pike v7.6 release 86 Copyright %Gï¿½%@ 1994-2006 Link%Gï¿½%@ping University >Pike comes with ABSOLUTELY NO WARRANTY; This is free software and you are >welcome to redistribute it under certain conditions; Read the files >COPYING and COPYRIGHT in the Pike distribution for more details. > >(15166557) /ee (erik eriksson)/------------------------------------- >

1 0

Re: Pike + Perl? Any issues?
by bertrand.lupart＠linkeo.com 25 Jan '07

25 Jan '07

> It also seems someone has removed it from Pike7.7, so that particular > someone apparently doesn't want it maintained either. Noone was actually maintaining it, nor using it until now, apparently. If this module isn't maintained enough to be distributed mainstream, it would be good to have it in Monger with a big warning concerning it's usability. -- Bertrand

1 0

Pike + Perl? Any issues?
by Alexander Demenshin 24 Jan '07

24 Jan '07

Hi, I would like to use Perl from Pike, are there any issues? How stable/leak-free is Perl module? /Al

3 2

Instant rsif:esque functionality
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 22 Jan '07

22 Jan '07

In needing a tool to convert files between utf8 and ascii with above-ascii code points escaped \xXX or \uXXXX, I just ended up refactoring rsif a bit. We now have a shiny process_files.pike in Tools.Standalone which you can inherit, providing a process callback of your own. This is what rsif looks like now: #! /usr/bin/env pike inherit Tools.Standalone.process_files; string version = ("$Revision: 1.5 $"/" ")[1]; string description = "Replaces strings in files."; string usage = #"[options] <from> <to> <files> rsif (\"replace string in file\") replaces all occurrences of the string <from> with the string <to> in listed files. The name of the files that were changed are written to stdout. Directories may be given instead of files, in which case all the files in that directory will be processed. Available options: " + default_flag_docs; int want_args = 2; string process( string input, string from, string to ) { if( has_value( input, from ) ) return replace( input, from, to ); } Complete documentation is available in refdoc comments in the file; http://pike.ida.liu.se/development/cvs/view.xml?module=Pike&file=7.6/lib/mo… As this makes writing rsif style hacks a mere pike expression or two, a logical next step would be some lazy person bringing this power kit right up to the pike command line, for instant ad-hoc directory tree processing goodness à la pike -e 'something'. That could make rsif the equivalent of "pike -p2 'replace(arg1,arg2)'" or similar. My own side dish hack quota just ran out for the day, but feel very free to pick up the ball! (Checked in to Pike 7.6 and 7.7.)

4 8

Re: Default cast LFUN
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 22 Jan '07

22 Jan '07

(Dang. Wordy post, and almost completely unrelated to my proposal.) > I guess I'd be in favor of it, but yet I'm not terribly excited about > it. I wonder why... Casting is unfortunately an often useless and ill designed feature in Pike; that might account for some of the dispassion. You can only cast to primitive types, and value casts don't necessarily work, even if you know a value to be a string and want to cast it to an int, when declared a string|int. It's a system difficult to grow incrementally better too, unfortunately. Even though in some ways it's a syntactically very powerful operation on recursively casting a large data structure into another, using compound type casts like (array(string)). It just doesn't reach do all that much more, when you don't primarily work with primitive types. I'm not really bashing the lack of design in Pike; its evolved nature is what makes it good, too. But casts, at least to me, feel a bit like a dead end. The thought crept up on me after reading The Pinocchio Problem, http://steve-yegge.blogspot.com/2007/01/pinocchio-problem.html -- while not technically dead code, pike and casting feels like it has hit an evolutionary dead end. Small convenience changes like the one suggested might be within reach, but order of magnitude improvements are out of reach. With a bit of luck I just might know too little of pike's internals to be right about this.

4 5

Default cast LFUN
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 22 Jan '07

22 Jan '07

Would implementing a default cast("string") implementation for objects that lack one be a good idea, if they respond to _sprintf("%s")? It is somewhat magical. The same could theoretically apply to int/%d, but I have a feeling it might be more questionable. Even more, float/%f. Any thoughts? Lessons learned from automatic _sprintf decoration have been largely positive, in my experience. (That might not imply anything about this proposal, though. It would, for instance, rarely throw errors about a missing cast implementation, in concert with the _sprintf decorator.)

3 4

Re: Problems with an circular free_object()
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 10 Jan '07

10 Jan '07

>OK, that all makes sense to me, but if I've missed an add_ref() in my >code, shouldn't that cause the object to be freed or destructed >prematurely? I added an add_ref(o) to my code to prevent this >problem, but the result was that the objects weren't getting freed. >I've stepped through a simple program that exhibits the problem, and >that object comes to schedule_really_free_object() numerous times, >each time with a refcount of 0 or -1. I've noticed that once it >finally enters its endless loop, o->next == o... shouldn't that cause >the loop to stop? Please check if o->prog is still set the second time. If it is, and the object is on the top of the objects_to_destruct queue, the queue will become circular, and when the destruct pass comes it will loop forever. >Bill

1 0

Problems with an circular free_object()
by H. William Welliver III 10 Jan '07

10 Jan '07

I've been having a problem with pike going into what seems like an infinite loop while exiting. The problem seems to occur with objects from my Objective-C module, and it's something I noticed before, but "solved" by adding a ref so that the objects were never freed. I fixed that problem last night, and now the problem is back. The backtrace looks like this: #0 schedule_really_free_object (o=0x1812038) at /Users/hww3/Pike/7.7/ src/object.c:1068 #1 0x00016610 in low_return () at /Users/hww3/Pike/7.7/src/ interpret.c:2018 #2 0x0001697c in jump_opcode_F_RETURN_0 () at /Users/hww3/Pike/7.7/ src/interpret_functions.h:1601 #3 0x007d5260 in ?? () #4 0x0001a76c in catching_eval_instruction (pc=0x1039114) at /Users/ hww3/Pike/7.7/src/interpret.c:2212 #5 0x0001a864 in jump_opcode_F_CATCH () at /Users/hww3/Pike/7.7/src/ interpret_functions.h:1273 #6 0x01039108 in ?? () #7 0x000181ac in mega_apply (type=25239608, args=2, arg1=0x13, arg2=0xffffffff) at /Users/hww3/Pike/7.7/src/interpret.c:2180 #8 0x00003644 in main (argc=2, argv=0xbffff974) at /Users/hww3/Pike/ 7.7/src/main.c:569 and if I step through the code, I eventually get back to the same point with the same object, and Pike never exits. Anyone with some internals experience care to venture a guess as to what the problem might be? Bill

3 2

pike internals documentation?
by Martin Bähr 05 Jan '07

05 Jan '07

hi, i just noticed that for some reason the chapter on pike internals which can be found in an old version of the pike manual is not there anymore in the current version: http://fredrik.hubbe.net/pike/tutorial/tutorial_split_17.html i think there are more useful sections in that old manual that are not in the current one. i noticed this one because of people repeatedly looking for documentation on the master, and that seems to be the only place where that documentation seems to still exist. anyone know why this has been dropped? intentional (because it's maybe outdated)? or by accident (lost during restructuring of sections)? or is it simply waiting to be converted to the new doc format? greetings, martin.

4 5

Jump to page:

2026

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