?

Log in

Previous Entry | Next Entry

Bugs on top of Bugs

At work I had a bug assigned to me. I fixed the bug last week, and today was the first chance I got to test it in a realistic environment. Sadly I appear to have made the behavior worse than before. I did fix the bug, but introduced a new, and harder to find bug. It is extremely frustrating, because on visual inspection of the code everything looks correct. Obviously it is not.

My fear is that it is some subtle Java behavior I am unfamiliar with since Java is still a new language to me.

Stupid bugs.

Comments

( 2 comments — Leave a comment )
raaga123
Aug. 8th, 2007 02:14 pm (UTC)
Is it anything you can put out there as a code snippet for others to look at? Java does have a few gotchas....
grieve
Aug. 9th, 2007 04:32 am (UTC)
Well by the time I saw your comment, I had already fixed the bug. :)

The basic problem turned out to be a simple deadlock shared across two classes. I am still new to the java threading primitives, so the error didn't jump out at me like it would have in C++. With a fresh set of eyes, and a few minutes of debugging I was able to track it down pretty quickly. In hindsight of course it seemed so painfully obvious.
( 2 comments — Leave a comment )

Latest Month

July 2011
S M T W T F S
     12
3456789
10111213141516
17181920212223
24252627282930
31      

Page Summary

Powered by LiveJournal.com
Designed by yoksel