Community
Participate
Working Groups
Using CDT 8.8.0.201508011003 Often, I debug a process that uses a library with no debugging symbols. In the Debug view, in only shows the address, without the library name. In this case, I have to resort to opening the Modules view and doing a visual binary start using the base address + size of the libraries to find in which library that stack frame is. Once I find it, then I can either download debugging symbols or compile it myself. Visual Studio does display the module names in its Call Stack view: http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-45-92-metablogapi/1754.clip_5F00_image003_5F00_489F8552.png
Created attachment 264883 [details] GDB shared libraries
Would still very much like that. Gdb does display the module name ;)