Date: Thu, 09 Mar 2000 21:42:20 -0500 From: Jim Bloom <bloom@acm.org> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: jdp@polstra.com, jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: More "ld-elf.so.1: assert failed" messages Message-ID: <38C8610C.E17A41EF@acm.org> References: <13611.952595759@zippy.cdrom.com> <200003100054.BAA64158@saturn.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
NOTE: Take everything I say here as general info. I haven't used these thread packages, but have used others in the past. It should be called somewhere between the starting of the process and the creation of the second thread. There is no problem if there is only one thread. THREAD Create would be fine as long as it sets a variable accessible to all threads indicating dllockinit has been called. Another possible location would be a routine that initialize the multithreading for the process. This routine may not exist in all thread packages though. Jim Bloom bloom@acm.org Juergen Lock wrote: > > In article <200003091645.IAA40726@vashon.polstra.com> you write: > >In article <13611.952595759@zippy.cdrom.com>, > >Jordan K. Hubbard <jkh@zippy.cdrom.com> wrote: > >> > The other possibility would be to fix the wine port so it calls > >> > dllockinit() to set up locking. I don't know for sure how hard that > >> > would be, but it's probably a feasible solution. > >> > >> To be honest, I'd be the most comfortable with this solution > > >... > >As far as I know, Wine is the only port that has problems with the > >version of the dynamic linker that's in -current at present. I've > >looked into adding the dllockinit() stuff to Wine, but could use > >some help from somebody who knows its internals better. > > Hm you could ask over in comp.emulators.ms-windows.wine... > > > I found > >the threads primitives, etc., but am not so sure where to place the > >dllockinit() call. > > When does it need to be called, just when starting a new thread? > (i have looked at the wine source before but never at ld-elf.so...) > And would this be the same on -stable and 4.0? Currently you > should be able to build a wine on a -stable box and it would still > run on 4.0 (well it wouldn't run _worse_ than on -stable), at least > thats the idea. > > Anyway if it should be called before a new thread becomes > runnable for the first the i think it could go in THREAD_Create > (in scheduler/thread.c), if it needs to be called from within > the new thread itself it looks like it should go in THREAD_Start > in the same source. > > HTH, > -- > Juergen Lock <nox.foo@jelal.kn-bremen.de> > (remove dot foo from address to reply) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38C8610C.E17A41EF>