Pike-devel August 2004

pike-devel@lists.lysator.liu.se

12 participants
34 discussions

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

17 Aug '04

I had kind of the same problem about 1½ ago. I needed to interface with my soundcard and thus needed ioctl. However, there was some argument against adding a general ioctl call, but I'm not sure what it was. I ended up using a tiny cmod for the purpose of setting my parameter. It might be that there is no real way of knowing what parameters are passed and how they should be interperted on the C-level. But that could be fixed using some smart heuristics, IMHO. / Marcus Agehall (PacketFront) Previous text: >2004-08-17 08:47: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >It seems like that ioctl is missing from Pike. :/ > >I wonder if ioctl should be added on a general basis, or if special >calls should be added for all ioctls... > >(crossposting developers list) > >Anyhow, it should be added somehow to src/modules/files/termios.c or >nearby. It shouldn't be too tricky. If I have time, I'll do it today >(so it lands in 7.7-cvs), but if not I'm leaving for austria tomorrow >morning, so can't do anything then for some weeks :/ > > / Mirar >

3 4

managing comport settings in linux
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 17 Aug '04

17 Aug '04

Not a good idea; the design philosophy of Pike is that Pike-level code should never be able to cause memory corruption at C-level. With ioctls there's no way to know what data a specific ioctl wants without reading the documentation for that specific ioctl for that specific OS. ioctls and fcntls are a way for device handlers to hook in APIs that aren't standard across all filedescriptors. / Henrik Grubbström (Lysator) Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

2 1

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

17 Aug '04

Can you guarantee that the process wont crash if you don't feed it the wrong information? / Mirar Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

1 0

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

17 Aug '04

It seems like that ioctl is missing from Pike. :/ I wonder if ioctl should be added on a general basis, or if special calls should be added for all ioctls... (crossposting developers list) Anyhow, it should be added somehow to src/modules/files/termios.c or nearby. It shouldn't be too tricky. If I have time, I'll do it today (so it lands in 7.7-cvs), but if not I'm leaving for austria tomorrow morning, so can't do anything then for some weeks :/ / Mirar Previous text: >2004-08-16 23:47: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >I've narrowed it down to this please advise if this is possible in >pike. >They do this: >mdlns &= ~TIOCM_RTS; >ioctl(dmm,TIOCMSET,&mdlns) > >Which from "man 4 tty_ioctl" means: > >TIOCMSET const int *argp > set the status of modem bits. > >So they activly set the RTS (hardware control) bit high on the port. > >/Marc > > / Marc Dirix >

1 0

pike 7.6 for windows?
by Martin Bähr 14 Aug '04

14 Aug '04

hi, this is a report from the irc front. more and more chatters are are firing questions about a windows build for 7.6 in our direction and we have no urls to fire back at them. what is the status of a windows build? is there one? will there be one? what is the holdup? (explaining people why it's not there is better than just telling them "we don't know") ah, the last attacker just left, hope it remains peacefull for a while... greetings, martin.

6 5

CMOD questions
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 13 Aug '04

13 Aug '04

It's been a while since I did any cmods, but now I need to write one for work related stuff. All questions are in the context of late CVS 7.7. Q1: How should I define my classes to get the following function: > indices(Foo); ({ get_bar }) > object x = Foo(); > indices(x); ({ get_bar }) > get_bar(); Foo.bar(); Ie, I want a class within Foo that can only be instantiated using the Foo.get_bar() method. Q2: Is there a way that a Foo.bar() object (as described above) can access the variables defined in Foo? (The variables which are accessed thru the THIS-pointer that is.) References to where things like this is already done within the Pike-source is appreciated.

2 9

Pike Conference 2004 query
by hww3 ＠ Pike developers forum 12 Aug '04

12 Aug '04

Greetings! I'm working with Martin Bähr to set up a Pike conference later this year. We had a number of viable options (which was gratifying in itself), and we've narrowed these down to a proposed date and location. We wanted to get some feedback on that to see if there were any big conflicts with anyone out there (obviously, we'd like to have as many folks from IDA as possible, assuming they're interested :)) Right now, we're looking at a conference in Essen, Germany starting somewhere in the first full week of October, the 11th through the 17th. Ideally, the conference would include one or two weekend days so that those who are unable to get time from work would be able to attend. Once we get a date set, we can start working out the details... Any thoughts, comments, suggestions? Bill Welliver (self appointed conference co-chair :))

11 13

Re: killing threads
by Mirar ＠ Pike developers forum 11 Aug '04

11 Aug '04

It might be possible to send an exception to a thread and kill it that way. In many cases it would be enough if the thread got killed on backjumps/functioncalls/whereever other stuff are checked as well... / Mirar Previous text: >2004-08-11 15:35: >Subject: Re: killing threads >-------------------------------------------------------------------- >On Tue, 10 Aug 2004, Ken wrote: > >> Hello, >> >> In a multi-threaded app, is it possible to kill a thread through means >> other than the starting function returning? > >No, and the reason is that it is nontrivial to clean up the resources held >by the killed thread. > >Hmm... I guess it'd be possible to let check_threads_etc() throw an error >of severity level THROW_THREAD_KILLED. Feel free to experiment. > >> I've tried using the kill() function, but all the signals cause the >> entire app to die. >> >> Thanks for any input! >> >> -Ken > >-- >Henrik Grubbström grubba(a)roxen.com >Roxen Internet Software AB > > > > / Brevbäraren >

3 8

pike -x on local sources
by Bertrand LUPART 10 Aug '04

10 Aug '04

Hey *, I'm following the instructions on http://gotpike.org:8000/ to build Pike modules. While i manage building and installing modules remotely using monger without any problem, i can't figure out how to build and install a module whose sources are local. Quoting http://gotpike.org:8000/PikeModule.html: "When the tool is run from the module source directory, without any arguments, the tool will determine what steps need to be performed in order to build the module." For example, while i try to run "pike -x Public.Protocols.Jabber" from /usr/local/src/Public_Protocols_Jabber-1.0, i end up with "Could not resolv Tools.Standalone.Public.Protocols.Jabber. (Perhaps the installed pike tree has been moved.)" What am i missing? -- Bertrand LUPART Linkeo.com - R&D | http://www.linkeo.com/ +33 1 72 71 71 82 | 17, rue de la Banque - F75002 Paris Systèmes de gestion d'email entrant | Email management systems

3 8

Fail to build Module modref
by Kaos 10 Aug '04

10 Aug '04

Hi, Anyone has any idea why I get this error? kaos@jenna Lua $ pike -x module module_modref make PIKE_INCLUDES=-I/usr/include/pike PIKE_SRC_DIR=/usr/include/pike BUILD_BASE=/usr/include/pike MODULE_BASE=/usr/include/pike TMP_BINDIR=/usr/include/pike SRCDIR=. FULL_SRCDIR=/home/kaos/dev/pike/Lua/ TMP_MODULE_BASE=. PIKE_EXTERNAL_MODULE=pike_external_module CORE_AUTODOC_PATH=/usr/lib/doc/src/core_autodoc.xml SYSTEM_DOC_PATH=/usr/lib/doc/ SYSTEM_MODULE_PATH=/usr/lib/pike/modules LOCAL_MODULE_PATH=$$HOME/lib/pike/modules RUNPIKE=pike module_modref make[1]: Entering directory `/home/kaos/dev/pike/Lua' if test ! -d "./plib/modules" ; then \ mkdir -p ./plib/modules ; \ fi; if test "xlua.o" != "x" ; then \ /usr/include/pike/install_module module.so ./plib/modules/Public.pmod/Lang.pmod/___Lua.so ;\ fi; \ if test "xmodule.pmod.in" != "x"; then \ /usr/include/pike/install_module module.pmod ./plib/modules/Public.pmod/Lang.pmod/Lua.pmod ;\ fi make[1]: Leaving directory `/home/kaos/dev/pike/Lua' pike -x extract_autodoc --builddir=plib/refdoc --srcdir=plib/modules Extracting from /home/kaos/dev/pike/Lua/plib/modules/ Extracting from /home/kaos/dev/pike/Lua/plib/modules/Public.pmod/ Extracting from /home/kaos/dev/pike/Lua/plib/modules/Public.pmod/Lang.pmod/ Extracting file "/home/kaos/dev/pike/Lua/plib/modules/Public.pmod/Lang.pmod/Lua.pmod"... if test "Xlua.c" -ne "X"; then \ pike -x extract_autodoc --builddir=plib/refdoc lua.c; \ fi /bin/sh: line 1: test: Xlua.c: integer expression expected pike -x join_autodoc --quiet --post-process "plib/autodoc.xml" "plib/refdoc" make: *** No rule to make target `plib/autodoc.xml', needed by `module_modref.xml'. Stop. kaos@jenna Lua $ test "Xlua.c" -ne "X" -bash: test: Xlua.c: integer expression expected kaos@jenna Lua $ ls AUTHORS Makefile config.cache configure linker_options lua.cmod.compiled modlist_headers module.pmod.in plib CHANGES Makefile.in config.log configure.in lua.c lua.o modlist_segment module.so refdoc COPYING README config.status dependencies lua.cmod make_variables module.pmod pike_Lua.feature testsuite.in I have a lua.c file (generated from lua.cmod) in the current directory, with some Autdoc markup in it. But it seems that it's something with 'test' that gets bogus.. ? // Andreas

4 3

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