Buggy behaviors samples

[asterix5]

Hi everyone,

I am looking for case samples of buggy behaviors in Java that a developer can face during execution of programs.
What can be most frequently buggy behaviors while programming and debugging on Java?

As for instance, there can be cases where in a GUI program, there can appear buggy behaviors such that a graphical element can appear in a wrong location (ex. textbox or button), or it fails to appears when it should appear.

Does anyone have any idea about this kind of cases and more general classification of these cases?
Are there repositories that do classify this kind of cases?

Thank you in advance!

[Junky]

In my experience the most frequent errors are:

Spelling mistakes including incorrect case.
Mismatch brackets: curly, square and round.
Placing a semi-colon at the end of an if statement or loop.
Using == when comparing Strings.
Using i = i++. Although this does not come up nearly as often as it used to.

[DarrylBurke]

As for instance, there can be cases where in a GUI program, there can appear buggy behaviors such that a graphical element can appear in a wrong location (ex. textbox or button), or it fails to appears when it should appear.

Do you have an example to prove that statement?

Are there repositories that do classify this kind of cases?

Bug Database

db

[Junky]

D'oh!

I misunderstood. I thought you meant bugs introduced by the programmer but you mean bugs in the Java API.

[asterix5]

D'oh!

I misunderstood. I thought you meant bugs introduced by the programmer but you mean bugs in the Java API.

Sorry for not presenting the topic in a good and clear way.
I am speaking about the bugs that are done by the developer.
There are bugs in the code that don't make the program fail, so the program runs "properly" but there appear these buggy behaviors such I mentioned in the first post.

Let have a more simple example. You have a simple drawing program. You have functions that define drawing simple objects in specific color - red, but when you run it, it draws different color lines-blue.

My question was regarding developer's bugs, which are not classic bugs but "buggy behavior".

[asterix5]

Do you have an example to prove that statement?

I am speaking about the bugs that are done by the developer.

There are bugs inside code that do not make the program fail. The program runs normally but there appear these "buggy behaviors" such the example with the drawing line posted above.

I am interested to know these kind of "buggy behaviors" that developers face while developing and running applications.

Is there any kind of classification of these cases?

[Junky]

In that case the question is much harder to answer. There can be a gazillion different things a developer can do wrong to make the program perform incorrectly. I heard one of the space probes plummetted into the surface of the planet it was supposed to be orbitting due to a misplaced sign (a positive value should have been negative or vice-versa). Using && instead of || and vice-versa can produce unexpected results. I'm sure if you put your mind to it you could think of a dozen or more examples.