mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Seems the whole issue of a lack of coroutine support in Mudlet stems
from the host<->Lua state association done via luaInterpreterMap. Since
coroutines are their own Lua state, the appropriate host isn't locatable
and thus most functions crash.

It'd be nice to have support for this, because coroutines are pretty
useful, and being unable to call Mudlet C-api functions from them is
pretty limiting.

** Summary changed:

- handling coroutines
+ coroutine supprt

** Summary changed:

- coroutine supprt
+ coroutine support

** Changed in: mudlet
       Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/484513

Title:
  coroutine support

Status in Mudlet the MUD client:
  Confirmed

Bug description:
  Program received signal SIGSEGV, Segmentation fault.
  0x00000000004b9beb in TLuaInterpreter::Echo(lua_State*) ()
  (gdb) bt
  #0  0x00000000004b9beb in TLuaInterpreter::Echo(lua_State*) ()
  #1  0x00007ffff7990c41 in ?? () from /usr/lib/liblua5.1.so.0
  #2  0x00007ffff799bba9 in ?? () from /usr/lib/liblua5.1.so.0
  #3  0x00007ffff79907b7 in ?? () from /usr/lib/liblua5.1.so.0
  #4  0x00007ffff799099a in lua_resume () from /usr/lib/liblua5.1.so.0
  #5  0x00007ffff799dd0a in ?? () from /usr/lib/liblua5.1.so.0
  #6  0x00007ffff799de13 in ?? () from /usr/lib/liblua5.1.so.0
  #7  0x00007ffff7990c41 in ?? () from /usr/lib/liblua5.1.so.0
  #8  0x00007ffff799bba9 in ?? () from /usr/lib/liblua5.1.so.0
  #9  0x00007ffff799111d in ?? () from /usr/lib/liblua5.1.so.0
  #10 0x00007ffff79907b7 in ?? () from /usr/lib/liblua5.1.so.0
  #11 0x00007ffff7990832 in ?? () from /usr/lib/liblua5.1.so.0
  #12 0x00007ffff798c141 in lua_pcall () from /usr/lib/liblua5.1.so.0
  #13 0x00000000004b0c31 in TLuaInterpreter::call(QString&, QString&) ()
  #14 0x00000000004d07dd in TAlias::execute() ()
  #15 0x00000000004d1e2b in TAlias::match(QString&) ()
  #16 0x00000000004db674 in AliasUnit::processDataStream(QString&) ()
  #17 0x0000000000443f3a in Host::send(QString, bool) ()
  #18 0x00000000004c992b in TCommandLine::enterCommand(QKeyEvent*) ()
  #19 0x00000000004c9c91 in TCommandLine::event(QEvent*) ()
  #20 0x00007ffff6f70efc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
  #21 0x00007ffff6f78ce3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
  #22 0x00007ffff67c2c2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
  ---Type <return> to continue, or q <return> to quit---
  #23 0x00007ffff7001dfa in ?? () from /usr/lib/libQtGui.so.4
  #24 0x00007ffff7004370 in ?? () from /usr/lib/libQtGui.so.4
  #25 0x00007ffff6fdc493 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
  #26 0x00007ffff7005d0c in ?? () from /usr/lib/libQtGui.so.4
  #27 0x00007ffff4571bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
  #28 0x00007ffff4575588 in ?? () from /lib/libglib-2.0.so.0
  #29 0x00007ffff45756b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
  #30 0x00007ffff67eb1a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
  #31 0x00007ffff70054be in ?? () from /usr/lib/libQtGui.so.4
  #32 0x00007ffff67c1532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
  #33 0x00007ffff67c1904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
  #34 0x00007ffff67c3ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
  #35 0x00000000004415a6 in main ()

  
  Attaching 2 xmls that will help reproduce this. Import in, and use the "test99" alias.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/484513/+subscriptions