New controversial addition in v1.3
If you are a power user of Carbide or simply poking around the tools, you will notice the new window that is available and functional for emulation debugging in Carbide v1.3. You can access it via the toolbar ‘Window’->Open View->Modules View. Once open it will appear by default in the lower pane of the carbide, tabbed together with ‘Console’, ‘Executables’ view, etc. During a debug session it will be filled with the executables that are currently loaded into the emulator and you have the projects that build these executables in your workspace or added them to the “Executables” tab of your launch configuration.
Some people may be confused by this window, since it resembles the ‘Executables’ window functionality, that was well described in the blog by Ken in this entry.
The difference between these windows is that ‘Executables’ window has the list of all executables that are known to the Carbide, no matter whether they are loaded into the emulator or not and it is always filled and independent of the debug session. ‘Modules’ view will only be filled with the information during the debug session. This is so called run-time information about the debugging target. And the purpose of it is to show what is running on target that the debugger knows about and has control over. It will not show you the list of files, beloning to the executable but rather the list of methods and other symbols. Ever wondered why your breakpoints are not being hit?
When debugging with TRK you will not get this information in v1.3. I am adding this support now. And it should be there in v1.3.1. Please, let us know if you are confused or not sure if this view is really necessary or helpful or creates more confusion rather then provides useful info.
