lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Fri, Aug 30, 2013 at 8:48 PM, kamicc olo <> wrote:
Not that long time ago had some problems with Luasocket because there
was exported some internal socket/ symbols. Like buffer_init(),
buffer_add() and stuff like that.

You should check Your binary and Luasocket library for such a things
with something like "elfread -s ./binary_file".

Thanks for the tip... now that I found instances of buffer_init what do?

- Chris
On 8/30/13, William Ahern <> wrote:
> On Fri, Aug 30, 2013 at 11:54:53AM +0300, Chris Datfung wrote:
>> I have a lua script embedded within another program. The script uses
>> socket.http from the lua-socket CentOS package installed via yum. When I
>> run my program with the lua script enabled the program dies with a
>> segfault. I created a backtrace and saw the following:
>> #5  0x00397945 in luaopen_socket_core () from
>> /usr/lib/lua/5.1/socket/
>> No symbol table info available.
>> #6  0x003d7d3a in ?? () from /usr/lib/
>> No symbol table info available.
>> ...
>> Am I missing another package that supplies or updates the symbol table?
>> How
>> can I fix this?
> I'm not familiar with RedHat, but on Debian based systems installing the
> "-dev" version of a package will often install unstripped libraries.
> However, the problem is almost certainly in your application, and you've
> unhelpfully elided the trace of your code.
> Wild guess: this is a stack manangement problem; printf lua_gettop()
> wherever you're calling into Lua to see if it's growing.