Forum General More useful error log reporting?

Any issues or discussions relating to Flash development are welcome here.

More useful error log reporting?

Postby wildbunny » July 28th, 2011, 11:14 am

Hi guys,

I'm having trouble getting any joy out of the error log - some as3 errors give me the full-callstack which is very very useful, while others just give me the *first* function in the stack, which is useless since its always a message received...

And if I click on one of the less useful errors which occurs a lot, the details are no good either because they go off the screen and contain no more information...

I've attached two screen-shots :)

typeerror1.png
typeerror1.png (36.55 KiB) Viewed 2120 times


typeerror2.png
typeerror2.png (56.62 KiB) Viewed 2120 times


Cheers, Paul.
wildbunny
 
Posts: 217
Joined: March 9th, 2011, 10:35 am

Re: More useful error log reporting?

Postby Benjaminsen » July 31st, 2011, 9:34 pm

The reason you are not getting better error messages is that only the Flash Debug player provides stack traces etc. Naturally most of your users does not have the debug player installed and thus, they throw simple errors such as "Error #2007".

Or said in another way, we provide all the information about the errors we have. In your specific case you have a null reference error somewhere in your code.
Benjaminsen
.IO
 
Posts: 1444
Joined: January 12th, 2010, 11:54 am
Location: Denmark


Return to General



cron