Arc Forumnew | comments | leaders | submit | fredfred's commentslogin
1 point by fredfred 6134 days ago | link | parent | on: Unimpressed.

Impressed...by the walkthru on your link. I took the easy route for the failing mkdir and just created it from the command line.

I'm still confused how you're getting the server port open and I'm not. But then you don't seem to be having the problem with the shell out to the date command that I'm getting, so maybe you are running under cygwin?

-----

1 point by kens 6134 days ago | link

Yes, I'm using Cygwin. I still have no idea how to fix the 'srv thread took too long' problem, though.

-----

2 points by fredfred 6134 days ago | link | parent | on: Unimpressed.

Let me guess. You guys are running cygwin right?

For reasons I won't go into I can't. I'm attempting to get this running native. I can work around the date thing above by using library calls rather than shelling.

I suspect that the port problem is due to a difference defaults. I don't see 'localhost' or '127.0.0.1' being explicitely stated anywhere, and maybe it needs to be.

And yes, I have a sufficiently authorised user profile. I occasionally run various http servers and I frequently create tcp & udp servers using Perl & D & Haskell etc.

This isn't a case of the port not being bound, it isn't getting that far, otherwise my firewall would be telling me that it is trying to act as a server and asking me to authorise it. This is failing in a system call due to parameter errors and is probably correctable at the source code level, but I can't find where.

I'm still decidely unimpressed with the error reporting though. I might just as well say: "Oops, summat's up!". if it isn't going to give some indication of where.

-----

1 point by squirrel 6133 days ago | link

This thread seems like it might be relevant: http://www.cs.brown.edu/pipermail/plt-scheme/2006-January/01... In particular, http://www.cs.brown.edu/pipermail/plt-scheme/2006-January/01... gives some links that look at least interesting.

The abstraction is clearly leaking though: we are having to dig into PLT when we want to talk Arc.

Maybe a MzScheme expert can help us - surely there is a debug mode of some kind that lets you see what code is being executed?

-----

2 points by fredfred 6133 days ago | link

Yes. This seems to be an MzScheme/setup problem and little to do with arc.

I still think the error reporting/traceback situation is abismal, but I accept that this is probably the wrong place to get help in getting arc to run for my scenario.

-----

1 point by squirrel 6133 days ago | link

And yes, we are using Cygwin, but I don't think it's needed (I turned it off and Arc still ran).

-----

2 points by fredfred 6134 days ago | link | parent | on: Unimpressed.

That "The syntax of the command is incorrect." appears to be from arc.arc:1204

(def date ((o time (seconds)))

  (let val (tostring (system (string "date -u -r " time " \"+%Y-%m-%d\"")))

    (subseq val 0 (- (len val) 1))))
which could presumably be replaced with something from date.ss?

But it probably doesn't explain the error: "Error: "tcp-listen: listen on 80 failed" which only seems to appear in \lib\libmzsch352_000.dll

So, toast then?

-----

3 points by fredfred 6134 days ago | link | parent | on: Unimpressed.

c:\MzScheme\arc0>mzscheme -m -f as.scm

Use (quit) to quit, (tl) to return here after an interrupt.

arc> (defop said req

  (aform [w/link (pr "you said: " (arg _ "foo"))

           (pr "click here")]

    (input "foo")

    (submit)))
#<procedure:gs1430>

arc> (asv 80)

The syntax of the command is incorrect.

Error: "tcp-listen: listen on 80 failed (An address incompatible with the requested protocol was used.; errno=10047)"

That "The syntax of the command is incorrect." is probably a clue, but where to look and for what?

-----