Console errors have stopped

Solar2D General Questions/Discussion
#1

Long shot but…i was wondering if anyone else has experienced this…

The app i’ve been building stopped reporting errors to the console (and growl) while i’m developing. So now i’m coding blindly which is slowing me down a lot :frowning:

I can’t really say anymore… (cos i can’t post any errors here) so i appreciate this will probably turn into a dead thread quickly.

perhaps someone knows of a log file or something that may have the errors stored…

One thought…and again this is a long shot:
If one of my required files doesn’t contain the package seeall statement - does that run on a separate thread to the rest of the app? (in terms of console output)

Thanks
Mike [import]uid: 13758 topic_id: 10898 reply_id: 310898[/import]

#2

Hey there,

Firstly - this is NOT my area so I cannot provide a solution, but clearly it’s a big problem for you; I’d be tearing my hair out!

Are you able to file a bug report, please?

Peach [import]uid: 52491 topic_id: 10898 reply_id: 39772[/import]

#3

I am having the same issue – exceptions are being swallowed. Basically having to use print statements to see where the code stopped working. And I am tearing my hair out. :slight_smile: [import]uid: 17130 topic_id: 10898 reply_id: 39790[/import]

#4

Mac? Windows?

What build?

Any steps to reproduce?

C [import]uid: 24 topic_id: 10898 reply_id: 39797[/import]

#5

Thanks for getting back to us…
We have a main.lua which loads in a framework/page management class…

local framework = require(‘f_main’)

But in f_main.lua we DON’T have a package seeall statement.
If we add the seeall statement we regain our errors (but unfortunately the rest of the project breaks :frowning: )

Then, from f_main we do
local theGame = require(‘g_main’) (which DOES have the seeall statement)

If we then put a random error in the game file, we get no errors reported.
Corona Simulator: 2011.484 (2001.4.12)
Mac OSX 10.6.7

Hope I’ve been clear enough :expressionless:
Thanks for your time.
Mike
[import]uid: 13758 topic_id: 10898 reply_id: 39804[/import]

#6

local framework = require(‘f_main’)

But in f_main.lua we DON’T have a package seeall statement.
If we add the seeall statement we regain our errors (but unfortunately the
rest of the project breaks :frowning: )

–> why does it break? there is something you are doing that is beaking it. require needs seeall…

c [import]uid: 24 topic_id: 10898 reply_id: 39806[/import]

#7

If you layer module references a few levels deep then yes you can hide errors in the console. I used to do this to get round compile errors, it never fixed the problem but at least the error was swept away :slight_smile:

Creating a group and inserting something then you insert all that in another group with a nested function call from another module (with an error) should work but will not show the error and may crash :slight_smile: [import]uid: 33866 topic_id: 10898 reply_id: 39807[/import]

#8

I’ve only skimmed this post, but my initial guess is that stdout (io module) is out of scope…you should not have to use package.seeall in straight Lua, but Carlos knows the inner workings of Corona much better than I and if he says it’s required, I would listen. You can try overloading the built in function:

io.output

with your own function and then make sure io.output is visible (ie “io” module is referenced by a local var) inside of your private module

actually, if io is visible, you should not have to overload but this gives you the chance to intercept stdout…

let us know if this works [import]uid: 6175 topic_id: 10898 reply_id: 39896[/import]

#9

Hmmm,

I had in similar issue for a while. It turns out it was because I had the following line in my code:

debug=system.getInfo("environment")=="simulator"

It was well intentioned! A global debug boolean which controlled the print statements and debug rendering. Just like I used to do in Java.

Except it also overrides the Lua debug library! Suddenly the simulator crashed without an error at every typo and bug.

Being able to replace the reference to the debug library with a boolean value is part of the power and joy of Lua (I mean I could actually painstakingly replace all references to Color with Colour if I wanted to, which is great), but I wonder whether it might be possible to protect the Corona libs/simulator from this happening by them storing their own references to important libs?

I hope that’s solved your issue, otherwise good luck! [import]uid: 11757 topic_id: 10898 reply_id: 44167[/import]

#10

personalnadir… you are a star!!!
That was exactly the problem. We can now see the errors reporting.
Thanks so much!
Mike [import]uid: 13758 topic_id: 10898 reply_id: 44172[/import]

#11

No problem! Glad to be a help.

I was caught out by that for 2 months I think. [import]uid: 11757 topic_id: 10898 reply_id: 44188[/import]