KSE does not appear to work when I run FreeBSD 6.2 on VMware

[Julian Elischer]

Akshay Kawale wrote:
> I have an amd64 machine, but I'm using a generic FreeBSD kernel.
> My host OS is Ubuntu i386 (not amd64), so I'm not sure what is exported 
> to the guest.
> 
> My physical machine is a P4 however.
> Would that make a difference? (Considering my kernel/libc is compiled 
> for a generic i386/i686).
> 

is it an amd64 freebsd kernel or i386?

> - Akshay
> 
> ----- Original Message ----
> From: Julian Elischer <julian at elischer.org>
> To: Kip Macy <kip.macy at gmail.com>
> Cc: Akshay Kawale <freebsd_noob at yahoo.com>; freebsd-threads at freebsd.org
> Sent: Monday, October 8, 2007 11:17:27 AM
> Subject: Re: KSE does not appear to work when I run FreeBSD 6.2 on VMware
> 
> Kip Macy wrote:
>  > I can't speak to your problem directly.
>  >
>  > Two (somewhat) relevant comments:
>  >
>  > - For security reasons procfs is not mounted by default.
>  > - KSE is being supplanted by libthr.
> 
> 
> He's not using libkse but writing his own concurrancy app by using the
> primatives.
> 
> My question is whether he is on  amd64 or i386
> 
> 
>  >
>  > -Kip
>  >
>  >
>  > On 10/6/07, Akshay Kawale <freebsd_noob at yahoo.com> wrote:
>  >> Hi,
>  >>
>  >> I'm writing a small thread library based on KSE.
>  >> I've got some initial code ready that performs an upcall when I 
> create a new KSE.
>  >>
>  >> However, this code only works on a physical machine. When I run 
> FreeBSD on VMware, my program does not appear to perform the upcall. I 
> know that it's not upcalling because I intentionally seg fault in my 
> upcall function. (I also put a gdb breakpoint at the upcall function, 
> which does not hit).
>  >>
>  >> I've tried this on a stock 6.2 RELEASE Kernel (Physical Machine) and 
> on 6.2 RELEASE and 6.2 RELEASE-p8 (VM).
>  >>
>  >> My /proc does not appear to be set up, so I can't use 'truss' to 
> figure out if the KSE Syscalls are actually being called.
>  >>
>  >> truss: cannot open /proc/curproc/mem: No such file or directory
>  >> truss: cannot open1 /proc/1044/mem: No such file or directory
>  >>
>  >> I wrote a small threaded program using pthreads, and that appears to 
> work ok on VMware.
>  >>
>  >> Does anyone have an idea what could be wrong?
>  >> Any suggestions to help me debug?
>  >>
>  >> Thanks.
>  >>
>  >> - Akshay
>  >>
>  >>
>  >>
>  >>
>  >>
>  >>       
> ____________________________________________________________________________________
>  >> Shape Yahoo! in your own image.  Join our Network Research Panel 
> today!   http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
>  >>
>  >>
>  >> _______________________________________________
>  >> freebsd-threads at freebsd.org mailing list
>  >> http://lists.freebsd.org/mailman/listinfo/freebsd-threads
>  >> To unsubscribe, send any mail to 
> "freebsd-threads-unsubscribe at freebsd.org"
>  >>
>  > _______________________________________________
>  > freebsd-threads at freebsd.org mailing list
>  > http://lists.freebsd.org/mailman/listinfo/freebsd-threads
>  > To unsubscribe, send any mail to 
> "freebsd-threads-unsubscribe at freebsd.org"
> 
> 
> 
> ------------------------------------------------------------------------
> Yahoo! oneSearch: Finally, mobile search that gives answers 
> <http://us.rd.yahoo.com/evt=48252/*http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC>, 
> not web links.