Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

checkArgList failure prints empty string #411

Closed
raptor opened this issue Aug 22, 2015 · 3 comments
Closed

checkArgList failure prints empty string #411

raptor opened this issue Aug 22, 2015 · 3 comments

Comments

@raptor
Copy link
Contributor

raptor commented Aug 22, 2015

From buckyballreaction on March 11, 2014 22:56:36

What steps will reproduce the problem? 1. call an API method that internally uses checkArgList()
2. use an invalid argument
3. see the stacktrace? it doesn't print the error

For example, do this in a levelgen, in main():

bf:subscribe(Event.ShipEnteredTheTwilightZone)

That will fail the args check and trigger a stack trace... which prints empty strings for the stack.

Original issue: http://code.google.com/p/bitfighter/issues/detail?id=411

@raptor
Copy link
Contributor Author

raptor commented Aug 22, 2015

From buckyballreaction on March 26, 2014 20:58:47

Issue 413 has been merged into this issue.

@raptor
Copy link
Contributor Author

raptor commented Aug 22, 2015

From buckyballreaction on March 27, 2014 16:57:49

This is due to LuaJIT's exception handling... I have to fix issue #413 first (after I un-merge it)

@raptor
Copy link
Contributor Author

raptor commented Aug 22, 2015

From buckyballreaction on March 27, 2014 22:19:25

This is also magically fixed in r8c14ffc2727e , although some stack traces print a little weird with '\9' concatenated at the start and '\13' at the end of trace lines.

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant