CiderDebugger.lua:1381 Cider Stops and cant continue

Windows 7 version…
Cider Version 1.5.3 ( checked - its the latest

CiderDebugger.lua:1381
Runtime error: …ona-mobile\beta - projects\SampleApp\CiderDebugger.lua:1381: att
empt to index global ‘debug’ (a boolean value)

>> This is that line - which is at the end of --> function ->debugloop
debug.sethook ( debugloop, “crl”,0 )

If i just run my app in Cider it runs fine - but I wish to inspect the variables an table values.

But cant… Please help

Larry [import]uid: 11860 topic_id: 28312 reply_id: 328312[/import]

Hello Larry,

It seems the debug library has been overridden somewhere in your code. Please check for a

debug = true --please remember debug is a lua library  

or something like that in your code and localize it or change the name of the variable if you can. Please do not override the debug library.

Regards,
M.Y. Developers [import]uid: 55057 topic_id: 28312 reply_id: 114356[/import]

Confirmed same error on Mac Lion - ver 1.5.4 cider.

I am using _G.debug and have never had a problem in this project at anytime.

I have been debugging like crazy.

and in this module there is no _G.debug

Are you guys using _G.debug?

If so I can go through and change it everywhere I have it.

Larry
[import]uid: 11860 topic_id: 28312 reply_id: 114358[/import]

@M.Y.developers any other thoughts?

Larry [import]uid: 11860 topic_id: 28312 reply_id: 114360[/import]

Hello Larry,

I am using _G.debug and have never had a problem in this project at anytime

Most corona libraries do not use the debug library because they do not need it so when you override the library there are no ill effects. Cider however does use the library so you will need to change the name _G.debug to something else for now. Please note that to access a global you do not need to explicitly say _G.debug, you can just use debug.

you bring up a good point and we will cache the debug variable in the next release so this does not happen again.

Regards,
M.Y. Developers [import]uid: 55057 topic_id: 28312 reply_id: 114391[/import]

[RESOLVED] Well, you hit the nail on the head. I changed my debug switch from _G.debug to _G.DebugMode and now i’m back to debugging my bugs away.

Thanks so much for the assistance.

Larry [import]uid: 11860 topic_id: 28312 reply_id: 114402[/import]