Pike-devel September 2006

pike-devel@lists.lysator.liu.se

4 participants
15 discussions

A hefty cleanse
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 14 Sep '06

14 Sep '06

So Ssleay, Pipe, Perl and Mird are gone from 7.7. Was decided upon through a very enlightened consensus, I'm sure. Could we outsiders get a rundown on the rationale behind this too? Don't they work at all? Commit messages talk about removing from "standard Pike". Are they going to appear somewhere else?

4 5

Re: threading and externally created threads
by H. William Welliver III 12 Sep '06

12 Sep '06

I finally had some time to look at this, and native_dispatch() had exactly what I was looking for. However, I found a problem (at least for me) in THREADS_ALLOW(): when you call this macro, it checks if threads are enabled and the number of threads. If there are more than one thread, it unlocks the interpreter. The problem is, if you only have one thread when you call THREADS_ALLOW(), the lock doesn't get released and any code running in "temporary pike external" threads will just sit there. I imagine that this is only a problem for things like the java bridge and my code, but thought I'd mention it in case there's a simple solution. I have taken to starting a thread that simply enters a sleep () loop before creating my external threads, and this works just fine. Anyone have a better solution? Bill Thu Sep 7 10:25:01, Henrik Grubbström (Lysator) at Pike (-) developers forum wrote: > > I'm working on an Objective-C bridge for Pike, and I've got a problem > Take a look at src/modules/Java/jvm.c:native_dispatch(). > > Bill

1 0

developers at conference?
by H. William Welliver III 11 Sep '06

11 Sep '06

Will any of you guys be at the conference? I've got some questions about some ideas I have for the objective c bridge i've been working on, and figured it would be easier to have a conversation about it than try to do it via email.

4 3

epoll
by Peter Bortas ＠ Pike developers forum 07 Sep '06

07 Sep '06

It's an implementation detail if epoll syscall comes with a device of not, so is there some special reason the configure test checks for /dev/epoll? I'm currently forceing it to epoll in machine.h to get it to build on Debian stable.

1 0

threading and externally created threads
by H. William Welliver III 07 Sep '06

07 Sep '06

I'm working on an Objective-C bridge for Pike, and I've got a problem as it relates to threads that I'd like to get some input on. My module wraps Objective-C objects within Pike objects and the other way around. The problem I'm running into is when I try to create threads in Objective-C. I create the thread successfully (using NSThread). The new thread is supposed to run some c code that eventually finds a Pike function to run, pushes its arguments onto the stack, then calls the function with those arguments. When running in Hilfe, everything seems to work fine until I call apply_svalue(). At that point, Pike dies: > .NSClass("NSThread")->detachNewThreadSelector_toTarget_withObject_ ("run", dummythreadrunner(), .NSClass("NSString")->stringWithCString ("foo")); Whee! We're wrappin' an object, thread=-1610559648 PiObjCObject.methodSignatureForSelector: run (1) Result: 0 > PiObjCObject.forwardInvocation: run pushed args, thread=25755136 C stack overflow. src/modules/files/file.c:3913: Fd(0)->read (Public.ObjectiveC.dummythreadrunner()->run,"C stack overflow.\n") /usr/local/pike/7.6.86/lib/modules/Stdio.pmod/module.pmod:109: Stdio.File("stdin", "r", 777 /* fd=0 */)->read() /usr/local/pike/7.6.86/lib/modules/Stdio.pmod/Readline.pike:568: Stdio.Readline()->InputController()->run_blocking() /usr/local/pike/7.6.86/lib/modules/Stdio.pmod/Readline.pike:1603: Stdio.Readline()->edit("",UNDEFINED,UNDEFINED) /usr/local/pike/7.6.86/lib/modules/Tools.pmod/Hilfe.pmod:2258: Tools.Hilfe.StdinHilfe()->create(UNDEFINED) /usr/local/pike/7.6.86/lib/modules/Tools.pmod/Hilfe.pmod:0: Tools.Hilfe->StdinHilfe() As you can see, the thread is created, and code is running in the new thread. I've not released the thread lock in my code (it bails out either way), and until assign_svalue is called, all of the other calls to internal c-pike functions work successfully (see forwardInvocation PiObjCObject.m in CVS). Any suggestions about how I can solve this problem? source is available here: http://buoy.riverweb.com:8080/viewrep/cvs/pike_modules/Public_ObjectiveC Bill

2 1

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 September 2006