| RE: [cdt-debug-dev] contents of a binary object in the CDT views |
Mikhail, For what I'm looking to do, adding a custom content provider is overkill.However, it looks like I wasn't really asking the right question, or at least there was another more important question I should have started with. After some additional experimenting and exploring through the code, it occurred to me something interesting was going on.
The screenshots in my original email show the "new" way (as of changes in bugzilla 39640, Feb 2006) in which an IBinary builds its contents--not through IBinaryObject logic (reading the executable's symbol table), but by creating TranslationUnit children for the files reported by the debug information in the executable. The end result of both approaches is very different. One gives you a view based on what the source parser sees, the other gives you the view based on the actual symbols present in the executable. See the attached screenshot.
Each approach has its advantages and disadvantages. 39640 added a much needed capability to import an executable and create a project that could be used for debugging. However, that same feature took away the ability for the user to peer into the symbol table of the executable and set breakpoints/watchpoints that way. One could argue that the old way provides a low level, more accurate representation of the executable, where the new way provides a richer, but less reliable/truthful representation.
I think both are needed, and so I would like to table my original question (which is much simpler in scope) and see if anyone agrees that we should look at a way to let the user choose how he wants to view the Binary element.
Finally, I'll note, if it isn't obvious yet, that the content for both the executable in the C/C++ Projects view and the Modules view is calculated in the same way, using the same underlying logic. So, this issue is not really specific to the Modules view.
John At 09:47 AM 3/25/2007, Mikhail Khodjaiants wrote:
John,The Modules view's implementation is based on the flexible hierarchy API. You can provide your content, label and other element adapters to replace the view's content. The current implemenation adapts to ICElement labels and structure. If you mean to add new features to CDT, we need to find a way on how to get the information needed to display it.Mikhail ________________________________ From: cdt-debug-dev-bounces@xxxxxxxxxxx on behalf of John Cortell Sent: Fri 23/03/2007 19:59 To: CDT Debug developers list; CDT Debug developers list Subject: RE: [cdt-debug-dev] contents of a binary object in the CDT views Nope; not what I meant. The modules view provides extra information; I'm not looking to carry that over. I'm just talking about extending the criteria of what shows up in the list to cover assembler labels, which many assembler develops treat as functions. John At 02:57 PM 3/23/2007, Doug Schaefer wrote: >Did you mean make the CView look like the modules view with the extra type >information? I'd say yes. I find the symbols in binaries barely useful right >now. > >Doug Schaefer, QNX Software Systems >Eclipse CDT Project Lead, http://cdtdoug.blogspot.com > > > > -----Original Message----- > > From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev- > > bounces@xxxxxxxxxxx] On Behalf Of John Cortell > > Sent: Friday, March 23, 2007 3:52 PM > > To: CDT Debug developers list > > Subject: [cdt-debug-dev] contents of a binary object in the CDT views > > > > _______________________________________________ > > cdt-debug-dev mailing list > > cdt-debug-dev@xxxxxxxxxxx > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev >_______________________________________________ >cdt-debug-dev mailing list >cdt-debug-dev@xxxxxxxxxxx >https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev _______________________________________________ cdt-debug-dev mailing list cdt-debug-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev --IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you._______________________________________________ cdt-debug-dev mailing list cdt-debug-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
Attachment:
ss.gif
Description: GIF image
