StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POImplementing debugger support: choice of debugging API
primarykey
Id
1150424
data
AcceptedAnswerId
1157363
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-19T17:44:15.750
FavoriteCount
1
LastActivityDate
2012-06-06T05:22:21.263
LastEditDate
LastEditorUserId
0
OwnerUserId
138304
ParentId
0
PostTypeId
1
Score
2
ViewCount
648
LastEditorDisplayName
text
Body
The .NET Framework has unmanaged <a href="http://msdn.microsoft.com/en-us/library/ms404520.aspx" rel="nofollow noreferrer">debugging</a> and <a href="http://msdn.microsoft.com/en-us/library/ms404386.aspx" rel="nofollow noreferrer">profiling</a> APIs that I assume people/companies are familiar with. If someone was implementing debugger and profiler support for a new CLI runtime¹: <ul> <li>What would be the pros/cons of basic their operation on these existing APIs?</li> <li>These APIs retain backward compatibility² by incrementing interface extension numbers to indicate support for later features. I would have the opportunity to combine these interfaces and remove deprecated methods since there is no "backwards" to be compatible with. Would that be a good idea? One point of interest here is this would not remove source code compatibility with existing debuggers because my system would require the debugger be implemented in managed code & managed API, and the existing ones are written in unmanaged code.</li> <li>Are there other documented debugging/profiling APIs available? Is their feature set anywhere near as complete as the ones mentioned above?</li> </ul> ¹ I like working advanced, long-term projects at home to keep me learning and thinking about solutions to large problems. I know there are others available, but I want to work on one to really see what's involved, and I'm already a decent way into it. ² I can't find a link describing this, but it's extensively used in the Visual Studio API as well. I believe I saw it in a "COM interface naming guidelines" document? You see it as the <code>ICorDebugClass2</code> interface showing up to extend <code>ICorDebugClass</code> interface without altering the original.
Tags
<.net><design><debugging><api><clr>
Title
Implementing debugger support: choice of debugging API
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSam Harwell
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POImplementing debugger support: choice of debugging API
 UserUserId
 USSam Harwell
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POImplementing debugger support: choice of debugging API
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POImplementing debugger support: choice of debugging API
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.