mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Attached is a fix.

** Changed in: mudlet
     Assignee: (unassigned) => Vadim Peretokin (vperetokin)

** Changed in: mudlet
       Status: Confirmed => Fix Committed

** Patch added: "fix bug 525449.diff"
   https://bugs.launchpad.net/mudlet/+bug/525449/+attachment/2563862/+files/fix%20bug%20525449.diff

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

Title:
  Bad reporting of errors inside event handlers

Status in Mudlet the MUD client:
  Fix Committed

Bug description:
  When you get an error that happens inside a function that is called by
  an event handler, Mudlet will:

  a) Not report it to the debug console at all, instead reporting it to stdout
  b) Not report the exact location of the error, but just use the event handler name 

  ie for 
  function abc()
  	a = a + 1
  end

  That is attached to "some event" event, Mudlet will print the following to stdout and not to debug:
  LUA: ERROR running script  "abc"  ERROR: Lua error:some event 

  The proper error is also:
  attempt to perform arithmetic on global 'a' (a nil value) but not the event handler name like it does.

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