Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Connecting people working on the same problem within an IDE environment

IP.com Disclosure Number: IPCOM000028866D
Original Publication Date: 2004-Jun-04
Included in the Prior Art Database: 2004-Jun-04
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Abstract

This invention solves the problem of when many developers on large development projects encounter and start to debug the same problem within a similar period, and do not realize that others are looking at the same problem and do not have the same information relating to what caused the problem.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 1

Connecting people working on the same problem within an IDE environment

This invention provides for a hook in an exception monitor of applications under development within an IDE environment, and looks at the modules added to debug and in what routine's breakpoints have been established to determine if two people are likely debugging the same problem, and if these behaviors are similar enough they will inform users about other user's activities.

     This invention will save a problem signature in a shared database for a period of time and when another user creates the same or a similar signature within a particular period of time, each user is notified that the other user seems to be or has been working on the same problem.

     The users need not be actively debugging at the same time since the signatures are saved through debug sessions. The notification will indicate when the other user's signature was saved, and whether the other user is currently active.

     The signature includes any exceptions seen from one of the programs under debug, prior to or during debug. The exception types and positions within the code are saved as part of the signature. Locations within the debugger and whether the user has stopped or set breakpoints are also kept. Each entry in the signature is also given a significant score. Events that occur less often are given less significance than events that occur more often. For example, if a user typically sets a breakpoint at a particular point in t...