Jump to content
  • 0

Question

Posted

hello, i have got a serious problem and i would like to hear serious replys.

So, if i am writing a code, i compile it and there are 0 errors, i run the code and it stops working after some problem. This problem can be null pointer exception, casting to wrong class, just everything that eclipse cant find while compiling. The problem is, it just stops working, i cant see any error.

For example when i make table with 4 elements, and i try to get to element 5, eclipse cant find it, when i run such code, whole method stops, and there isnt any error.

It just drives me crazy, i use some russian h5 shitpack but maybe u guys know what can be a problem?

7 answers to this question

Recommended Posts

  • 0
Posted

For example when i make table with 4 elements, and i try to get to element 5, eclipse cant find it, when i run such code, whole method stops, and there isnt any error.

that should throw IndexOutOfArrayExcetion that can be catch in any method of the stack and ignored (that is kinda useles) try to check your code and try to use logs to find where is the problem

  • 0
Posted

Errors doesnt appear on any method, it doesnt matter if there is Try{}Catch{}, Throw Exception or not.

  • 0
Posted

hello, i have got a serious problem and i would like to hear serious replys.

So, if i am writing a code, i compile it and there are 0 errors, i run the code and it stops working after some problem. This problem can be null pointer exception, casting to wrong class, just everything that eclipse cant find while compiling. The problem is, it just stops working, i cant see any error.

For example when i make table with 4 elements, and i try to get to element 5, eclipse cant find it, when i run such code, whole method stops, and there isnt any error.

It just drives me crazy, i use some russian h5 shitpack but maybe u guys know what can be a problem?

You can parameter level affinity of the logs. Be sure in Logger properties you got enough affinity. If let's say, your warning stuff in try/catch block is under "warning", and the affinity level is put to "finest", you won't see anything.

 

In addition to that there's also an on/off value.

 

Best would be to ask directly to pack devs, and if you haven't access legally, change of pack.

 

http://docs.oracle.com/javase/1.4.2/docs/api/java/util/logging/Level.html

Guest
This topic is now closed to further replies.


×
×
  • Create New...