To locate the source of this bug, we performed the following tasks: Task #1 Based on the bug's description we reproduced its occurrence in a concrete drawing, as illustrated in Fig. 11. Figure 11a shows the original drawing.
To locate the source of this bug, we performed the following tasks: Task #1 Following the description at Source Forge we were able to reproduce the bug in the following way: (a) we created a diagram with one circle and one rectangle, with different filling colors; (b) we marked the circle and selected the "PickAttribute" button; (c) we marked the rectangle and selected the "ApplyAttribute" button.
We also reported a study where OGs have been successfully used to locate the defective program elements responsible for bugs reported by real users of the JHotDraw system.
In the following subsections, we describe how we have used the proposed OGs to locate the components responsible for these two bugs.
Effective methods for automatically locating bugs from bug reports are highly desirable (Saha et al. 2013), as they would shorten bug-fixing time, consequently reducing software maintenance costs (Zhou et al. 2012).
This is a bug, and we have located the problem.
Given their importance in the system domain, the names of such (class or method) abstractions are often the target of reflection when someone is either reporting or locating a bug.
The lucky receipient of that was a man named Sergey Glazunov, who located a bug that Google is calling, "High Integer overflows in WebKit JavaScript objects".
Testbirds has more than 25,000 testers signed up to its current crowd-based testing platform — most, but not all of whom are based in Europe — to kick the tyres of companies' apps for them to help locate bugs and do things like user interface testing.
Initially, we questioned whether current state-of-the-art bug localization techniques based on structured information retrieval, i.e., BLUiR, BLUiR+, and AmaLgam, would effectively locate bugs in C# projects.
We unfold our general goal in the following research questions: RQ1: Are BLUiR, BLUiR+, and AmaLgam effective to locate bugs in C# projects?
