Pike-devel August 2004

pike-devel@lists.lysator.liu.se

12 participants
34 discussions

Segfault in backend
by David Gourdelier 23 Aug '04

23 Aug '04

Hi, While trying the Shuffler module, I had the following segfault: #0 0x0809ba20 in really_free_compat_cb_box () #1 0x406887d0 in f_Shuffle_create () from /usr/local/pike/7.6.13/lib/modules/Shuffler.so #2 0x08074ee1 in low_mega_apply () #3 0x0807608e in mega_apply () #4 0x00000004 in ?? () #5 0x088c1124 in ?? () #6 0x0000000b in ?? () #7 0x00000000 in ?? () #8 0xfffce50c in ?? () #9 0xbf7ff624 in ?? () #10 0x080dfbd7 in call_pike_initializers () Previous frame inner to this frame (corrupt stack?) The really_free_compat_cb_box function is located in backend.cmod so I guess it's backend related. The problem is 100% reproductible and I can add any debug/line of code to help for fixing it. I'm using pike 7.6.13 from CVS (built the 15/08) / David

5 6

pike -t5 fails
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 23 Aug '04

23 Aug '04

I've compiled pike 7.7 from recent CVS with CONFIGARGS="--with-debug --with-rtldebug --with-dmalloc --without-copt". The resulting binary is executable and seems to work. However, when trying bin/pike -tX (X>1), the binary fails to start hilfe. Am I the only one with this problem or can someone reproduce this behaviour?

2 2

Pikefarm client problem
by Mikael Brandström 23 Aug '04

23 Aug '04

Hi, today I tried setting up the xenofarm client to compile pike on my Mac. It is running MacOS 10.3.5 (i.e. Darwin 7.5.0) and fink. Compiling Pike suceeds (I've tried it outside xenofarm), but xenofarm fails when assembling the result with the following lines from the xeonfarmclient.txt: BEGIN response_assembly PASS END cd build/xenofarm && tar cf - . > ../../xenofarm_result.tar tar: ./compilelog.txt: file changed as we read it tar: Error exit delayed from previous errors make: *** [xenofarm] Error 2 Any clues on how to fix this error? cheers, Mikael

7 17

CMOD and namespace placement
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 23 Aug '04

23 Aug '04

I want to write a module Bar that should work like a pmod-file and that should appear within the Pike namespace as Foo.Bar. What is the (best) way of doing that using CMOD?

1 0

pike 7.6 bump version ?
by Xavier Beaudouin 22 Aug '04

22 Aug '04

Hello there, Can pike 7.6 be bumped version ? Because Bill have fixed some SSL problems that can help us @Caudium Group to identifiate the good pike to run with Caudium 1.3 ? 7.6.11 is from 01/07/2004... So it can be good to have 7.6.13 from August ? Thanks, /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 7.6.6-2 + MySQL-4.1.3
by Hedda (http://www.xnetz.com/kali/ tillbaka!) ＠ Pike (-) developers forum 22 Aug '04

22 Aug '04

While compiling Pike 7.6.6-2 with MySQL-4.1.3: Compiling /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c: In function `f_shutdown': /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c:1101: error: too few arguments to function `mysql_shutdown' /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c:1113: error: too few arguments to function `mysql_shutdown' WARNING: Compiler failure! Trying without optimization! cc1: warning: -Wuninitialized is not supported without -O /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c: In function `f_shutdown': /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c:1101: error: too few arguments to function `mysql_shutdown' /home/roxen/Pike-v7.6.6-2/src/modules/Mysql/mysql.c:1113: error: too few arguments to function `mysql_shutdown' Seems like the MySQL header-file has changed to: int STDCALL mysql_shutdown(MYSQL *mysql, enum enum_shutdown_level shutdown_level);

2 1

Re: Inherited files being compiled
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 22 Aug '04

22 Aug '04

It's intentional that the master register programs that fail to compile. The reason is to avoid cascade errors when the same module is resolved repeatedly. / Martin Stjernholm, Roxen IS Previous text: >2004-07-08 10:04: >Subject: Re: Inherited files being compiled >-------------------------------------------------------------------- >I'll just send this e-mail to you directly. I'm not sure if I found the problem or not but it seems as if the unregister function inside of the master object is being called like it should. I did end up fixing the problem by calling the unregister function by my own means which I will show you below: > >//! This function is called when we want to clone an object >object|int clone_object(string sFile) >{ > /* Remove unneccesary parts */ > if(sFile[0] == '/') > { > sFile = sFile[1 ..]; > } > > /* Prepend the filename to include the path to Emage */ > sFile = "C:/EMAGE/" + sFile; > > /* Make sure the path is relevant to pike standards */ > sFile = normalize_path(sFile); > > if(programs[sFile]) > { > return ((program)sFile)(); > } > > /* Check to make sure the file exists */ > if(file_stat(sFile)) > { > program p = 0; > > mixed err = catch > { > p = compile_file(sFile); > }; > > if(err) > { > unregister(p); > > sscanf(sFile, "C:/EMAGE%s", sFile); > > Send("Error compiling " + sFile + ". Please fix any/all errors.\n"); > return 0; > } > else > { > /* Return the cloned object */ > return (p()); > } > } > > /* Throw an error if file does not exist. */ > error("File " + sFile + " not found.\n"); > > /* No file exists return 0 */ > return 0; >} > >I hope this helps in one way or another. It seems to me as if the calling program to be compiled is not the one being unregistered by the compiler but yet the inherited file is the one being called. Just an off the wall idea. I am in no way a professional programmer. Thanks for your suggestion anyways though. > >"Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum" <10353(a)lyskom.lysator.liu.se> wrote: >Try running pike with --autoreload. > >/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) > >Previous text: >>2004-07-08 02:15: >>Subject: Inherited files being compiled >>-------------------------------------------------------------------- >>I have what seems to be a simple problem but is causing me a huge headache. The problem is that if an inherited file does not compile it still adds that file to master->programs. Now I am not sure if that has anything to do with it but doesn't this cause the file not to be recompiled when called again? I am just wondering if there was a fix I could plug in so all i would have to do is make the fix, upload the file and carry on instead of having to restart the master. >> >> >> >>--------------------------------- >>Do you Yahoo!? >>New and Improved Yahoo! Mail - 100MB free storage! >> >> >> / Brevbäraren >> > > >--------------------------------- >Do you Yahoo!? >Yahoo! Mail - Helps protect you from nasty viruses. > > > / Brevbäraren >

1 0

out of memory in allocate
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 19 Aug '04

19 Aug '04

I would like to have the following > allocate(1617191936); Program received signal SIGSEGV, Segmentation fault. 0x08092695 in low_allocate_array (size=1617191936, extra_space=0) at /home/nilsson/Pike/7.7/src/array.c:118 118 ITEM(v)[e].u.integer=0; generate an out of memory message instead (if indeed that is the problem). But the malloc call do returns a pointer, so I don't know what is wrong.

7 18

managing comport settings in linux
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 17 Aug '04

17 Aug '04

Can you ever with these things? It all boils down to the fact that ioctls are very lowlevel, system specific and you shouldn't poke around with them unless you know what you are doing. By implementing my suggestion, you can implement default ioctls for "standard" functions and the user can easily implement her own ioctls as needed. But, since this is dangerous stuff for the average user-joe, I would suggest making it a compiletime feature which has to be enabled with --enable-user-ioctls or something similar. / Marcus Agehall (PacketFront) Previous text: >2004-08-17 13:35: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >Can you guarantee that the process wont crash if you don't feed it the >wrong information? > > / Mirar >

5 5

managing comport settings in linux
by Marc Dirix ＠ Pike developers forum 17 Aug '04

17 Aug '04

Ok I'll have go on it. /Marc / Marc Dirix Previous text: >2004-08-17 14:36: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >Sorry. Lost my CVS-repository to a fsck a few months ago. However, it >is not very hard to fix up a cmod that accomplishes what you need. > >Look at some (fairly simple) cmod in the pike source and I'm sure you >can figure it out. I usually start with the Bz-module, rip out almost >everything and then add my stuff. Just copy the post_modules/Bz dir to >post_modules/MyIOCTL and start changing... ;) > > / Marcus Agehall (PacketFront) >

1 0

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