On Wed, May 8, 2013 at 10:13 AM, Roberto De Ioris <[email protected]> wrote:
> > I am pretty frustrated, but go developers "way of thinking" is exactly the > opposite of mine (they do not want to be unix-centric, and maybe it is a > good thing for them). I tend to respect everyone (expecially project > owners) so lets' move on. > I see your frustration - it is a difficult one, but it's good that you're taking a pragmatic view of the situation in the face of this setback. > > I am heavily studying the gccgo project, and maybe it is a better approach > for uWSGI (in the short term) > > Go 1.0.x continue to be supported, as well as go 1.1 without > master,processes, mules, spoolers (ehm, what remains ???) > Does that reduce the value proposition of uwsgi + Go? > > Regarding your problem, i have rechecked and it works for me, maybe you > need to rebuild your plugins/go/pkg/*/uwsgi.a module (just remove it) I have just done a clean rebuild of 9ec20f2 and the reload seems to work now. The next issue I have come across is that whilst the touch-reload seems to be working, the touch-exec doesn't seem to trigger. If I put something bogus in, e.g. touch-exec = /home/foobar/bogus go build main.go uwsgi correctly reports that it can't stat the file named bogus. If I put the full correct path in, e.g. touch-exec = /home/foobar/main.go go build main.go Nothing seems to happen. However, if I put the unqualified path in, e.g.: touch-exec = main.go go build main.go I get the following: gracefully (RE)spawned uWSGI master process (pid: 5364) spawned uWSGI worker 1 (pid: 5368, cores: 1) mach error semaphore_wait: 15 fatal error: mach error goroutine 1 [runnable]: uwsgi._Cfunc_uwsgi_init(0x2, 0x15200000, 0x0, 0x400000001) uwsgi/_obj/_cgo_defun.c:149 +0x2f uwsgi.Run() uwsgi/_obj/_cgo_gotypes.go:4211 +0xef main.main() /Users/0x6e6562/Workspace/src/main.go:33 +0x13a goroutine 2 [syscall]: spawned uWSGI http 1 (pid: 5369) DAMN ! worker 1 (pid: 5368) died :( trying respawn ... Respawned uWSGI worker 1 (new pid: 5370) mach error semaphore_signal: 15 fatal error: mach error goroutine 1 [syscall]: [fp=0x4730e08] runtime.cgocallbackg(0x7fff5fbfe730, 0x7fff5fbfe7b8, 0x0) /Users/0x6e6562/Workspace/go/src/pkg/runtime/cgocall.c:272 +0x153 [fp=0x4730e28] runtime.cgocallback_gofunc() /Users/0x6e6562/Workspace/go/src/pkg/runtime/asm_amd64.s:635 +0x71 [fp=0x4730e30] return() /Users/0x6e6562/Workspace/go/src/pkg/runtime/asm_amd64.s:508 [fp=0x4730e78] runtime.cgocall(0x40015b0, 0x4730e90) /Users/0x6e6562/Workspace/go/src/pkg/runtime/cgocall.c:162 +0x128 [fp=0x4730e90] uwsgi._Cfunc_uwsgi_init(0x2, 0x15200000, 0x0, 0x400000001) uwsgi/_obj/_cgo_defun.c:149 +0x2f [fp=0x4730ee8] uwsgi.Run() uwsgi/_obj/_cgo_gotypes.go:4211 +0xef [fp=0x4730f90] main.main() /Users/0x6e6562/Workspace/src/main.go:33 +0x13a [fp=0x4730fb8] runtime.main() /Users/0x6e6562/Workspace/go/src/pkg/runtime/proc.c:182 +0x92 [fp=0x4730fc0] runtime.goexit() /Users/0x6e6562/Workspace/go/src/pkg/runtime/proc.c:1223 I'm wondering whether it may better to park this until you have done your research on gccgo? Cheers, Ben
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
