Pike-devel May 2004

pike-devel@lists.lysator.liu.se

11 participants
65 discussions

OpenBSD and pike...
by Xavier Beaudouin 26 Jul '04

26 Jul '04

Hello, According to http://pike.ida.liu.se/generated/pikefarm/7.7/97_28/verifylog.txt We have : Doing tests in modules/files/testsuite (94 tests) 0: ++++++++++ ++++++++++ ++++++++++ ++++++++++ ++++++++++ 50: ++++++++++ ++++++++++ ++++++++++ +++--+++++ Available fds: 1024 Forking... ok. Doing simple tests. Testing dup & assign. / Testing accept. -\|/-\| Testing uni-directional shutdown on socket Testing uni-directional shutdown on pipe Testing 12 sockets. /-\| Testing 16 sockets. /-\| Testing 20 sockets. /-\|/- Testing 24 sockets. \|/-\| Testing 28 sockets. /-\|/-\| Testing 32 sockets. /-\|/-\| Testing 36 sockets. /-\|/-\|/- Testing 40 sockets. \|/-\|/-\| Testing 44 sockets. /-\|/-\|/-\| Testing 48 sockets. /-\Accept returned 0, errno: 9 64 open fds: 0 - 63 [WATCHDOG] Pike testsuite timeout, sending SIGABRT. Abort (core dumped) *** Error code 134 Gdb says (http://pike.ida.liu.se/generated/pikefarm/7.7/97_28/core.txt) : Core was generated by `pike'. Program terminated with signal 6, Abort trap. #0 0x12793dd in poll () Active threads Backtrace #0 0x12793dd in poll () #1 0x7ddfda0 in _thread_kern_poll () #2 0x7ddf746 in _thread_kern_sched () #3 0x7ddf971 in _thread_kern_sched_state () #4 0x7dd9d73 in poll () #5 0x1c112353 in handle_timeouts (ignored=0x0) at /usr/home/kiwi/xenoclient/pike-7.7/obsd.home.oav.net/buildtmp/Pike- v7.7-snapshot/src/modules/HTTPLoop/timeout.c:192 #6 0x7dd703d in _thread_start () #7 0x1f in ?? () Cannot access memory at address 0xffffffff. This bug is here for ages... for both pike 7.6 and 7.7 (I don't have pike 7.4 on xenofarm even my box is sending data... so I cannot compare... do xenofarm does some "blacklisting ????").. Can I help to fix that ? /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

5 7

pike, sTeam and caudium at the linuxtag 2004
by Martin Bähr 21 Jun '04

21 Jun '04

hi, we have again been given the opportunity to present pike at the linuxtag in germany. from the 23rd to the 26th of june we will be able to present pike together with caudium and sTeam. please make suggestions on what to present, to make pike interresting to the public. who is willing to come to karlsruhe? if you bring a sleepingbag there is free accomodation. if you are interrested please contact me. (even if you are not sure you can make it, you don't need to commit right away) http://www.linuxtag.org/2004/ http://www.linuxtag.org/2004/community/pavillon.html http://www.infodrom.org/Debian/events/LinuxTag2004/projects.php3 http://www.infodrom.org/Debian/events/LinuxTag2004/faq.html greetings, martin. -- 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 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/ _______________________________________________ Caudium-general mailing list caudium-general(a)caudium.net http://lists.oav.net/wws/info/caudium-general Archives are : http://lists.oav.net/wws/arc/caudium-general Caudium Website : http://caudium.net/

3 3

Stdio.File sockets not getting closed in 7.6
by Bill Welliver 13 Jun '04

13 Jun '04

I've been battling a problem with 7.6 recently that I hadn't had in the 7.5 versions I'd previously been running. My code creates, over time, a large number of short lived Protocol.LDAP.client objects. The problem that I'm having is that even if I explicitly destruct these objects, I end up with a large number of sockets that are in CLOSE_WAIT state. Eventually, this number of sockets increases to the point where I run out of FDs. The only way to clear the sockets completely is to call gc(), which I've resorted to every 5 minutes through a call out to solve the problem. To me, this sounds like a problem. Anyone else have any thoughts? Bill

2 3

expected?
by Mirar ＠ Pike developers forum 31 May '04

31 May '04

Is this the expected behaviour when accidentally choosing a directory as the master? % pike -m . /home/mirar/pike/src/object.c:477: Fatal error: low_read_file(.) failed, errno=21 No stack - no backtrace. zsh: abort pike -m .

3 4

FreeType woes
by Fredrik (Naranek) Hubinette (Real Build Master) ＠ Pike (-) developers forum 31 May '04

31 May '04

Anybody here recognize this bug? http://fredrik.hubbe.net/hacker/viewtopic.php?t=162 Cliff notes: Image.Fonts.Font in Pike 7.6.6-2 fails to render images.

3 3

conference thoughts
by Bill Welliver 30 May '04

30 May '04

I was discussing the topic of the next Pike conference with Martin Baehr earlier, and we thought that it might be good to share our thoughts and get a discussion going. Basically, the conversation centered around 2 points: where to have it, and when to have it. On the first point of location, Martin has done some initial legwork. He's located a few potential locations, at least one of which has real potential in my mind. I'll let him talk about them if he feels it appropriate. The subject of when to have the conference is a little bit more important to me, as I'm starting a new job and need to know when I'm going to be away from work. Ideally, I'd like to be able to attend, and for that to happen, a date range somewhere between the middle of September to the beginning of October would be ideal. I say ideal because it gives us about a year since the previous conference, it's not in a peak vacation period for many people with jobs, and the weather hasn't turned unpleasant for those with travel/holiday plans incorporating the conference. For those who aren't keeping track, last year's conference ran roughly between the 24th and 28th of September in Paderborn, Germany. Any thoughts? Bill

11 17

Re: conference thoughts
by Leif Stensson, Lysator ＠ Pike developers forum 29 May '04

29 May '04

> Travel to Sweden is significantly more expensive for those of us > outside of Europe, not to mention hassle and time lost switching > airlines... : ) Of course. But I imagine roughly the same amount of hassle and expense occurs if the conference is in Germany, so I didn't mention that. :-) > Besides, if we're getting picky about location, wasn't the conference > the year before at Roxen HQ? (Not that I'm trying to be difficult or > anything) Actually, no. There were no Pike conferences at all before the one at Linköping University in 2002. There were brief visits at Roxen HQ during the Roxen User Conferences earlier years, but the conferences were not held at Roxen HQ, but rather in a specially rented movie theatre nearby. > One thing might be to consider locations where there are known pockets > of Pike developers that we might want to engage. There are a few in > europe east of germany, so perhaps that's a possibility too. Could be. Also, several of the countries east of Germany (including Poland, Estonia, Latvia, and Lithuania) joined the European Union earlier this month, after years of negotiations, so it has just become easier both for the people there to travel elsewhere in the EU, and for us to get to them. / Leif Stensson, Lysator Previous text: >2004-05-29 04:27: >Subject: Re: conference thoughts >-------------------------------------------------------------------- >Sounds like a good task for a group of his new pike students :) > >> Another possibility might be Dresden. Uwe Aßmann, who sponsored Pike >> development at Linköping University, is moving there this summer to >> start working at Dresden University. (I don't know if he has the time >> to arrange a conference there so soon after getting there, but it's >> a possibility.) >> >>> linköping is not much better however because for many it is to far >>> away and to expensive to get there. >> > >Travel to Sweden is significantly more expensive for those of us >outside of Europe, not to mention hassle and time lost switching >airlines... : ) > >Besides, if we're getting picky about location, wasn't the conference >the year before at Roxen HQ? (Not that I'm trying to be difficult or >anything) > >One thing might be to consider locations where there are known pockets >of Pike developers that we might want to engage. There are a few in >europe east of germany, so perhaps that's a possibility too. > >Bill > > > / Brevbäraren >

1 0

Events in pike?
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 29 May '04

29 May '04

Is there anyone except for me that likes to use events in their code? In several of my projects, I've implemented eventsystems with a register_event() method and a fire_event() method in a very simple fashion. The thought has occured to me, to write something more general and put it within Pike. But before I spend any time on it, I'd like some input on the matter. For instance, is it useful enough to write put in Pike? Would you like it to work in some special way? How do you normally implement events in Pike?

7 15

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

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