News : The level of daily SPAM has reached insane proportions, all registrations are now manual. I ask you to send me an e-mail (john (at) murga (dot) org), to confirm that you want me to create an account for you.

Post Reply  Post Thread 
socket.http bug or aminotdoinitrite?
Author Message

Posts: 113
Group: Registered
Joined: Jul 2007
Status: Offline
Reputation: 0
Post: #1
RE: socket.http bug or aminotdoinitrite?

That's weird. Executing the same code as you gives me this:

> r, e = socket.http.request("")
host not found
stack traceback:
    [C]: in function 'request'
    stdin:1: in main chunk
    [C]: ?

And it doesn't take down murgaLua, just the error. But indeed, normally r should be nil and e should be the error message, and no error should be thrown automagically.

I looked at this a bit further, and found out that it does work as expected in a plain Lua with the LuaRocks version of LuaSocket.
Apparently the only difference in the luasocket code between murgaLua and what I got from LuaRocks is this:

diff .//usocket.c /home/jpjacobs/software/murgaLua/3rd-party/luasocket-2.0.2-MOD/src//usocket.c
<         default: return hstrerror(err);
>         default: return strerror(err);

But this shouldn't matter because usocket isn't even being included in murgaLua, is it? So I think the problem must lie somewhere in the binding / build process...


This post was last modified: 12-28-2010 10:34 PM by jpjacobs.

12-28-2010 10:18 PM
Find all posts by this user Quote this message in a reply
Post Reply  Post Thread 

Messages In This Thread
RE: socket.http bug or aminotdoinitrite? - jpjacobs - 12-28-2010 10:18 PM

View a Printable Version
Send this Thread to a Friend
Subscribe to this Thread | Add Thread to Favorites

Forum Jump: