Community
Participate
Working Groups
The action is always disabled and appears broken. We should find a way to not show this action when DSF modules are being shown. This is actually a bug for CDT. But since it applies to DSF mainly, we need to create a patch for CDT to address it.
I took a liberty of re-purposing this bug to actuly fix this action rather then remove The main scenarios our customer want to support are the following: Case 1 startup: - application has 200 shared libs (!) - debugger startup takes forever with auto-solib - we turn off auto-solib for this - but now we want to load some stuff manually Case 2 attach: - we attach to application - we stop at random place and our backtrace looks like bunch on binary addresses - we load some librarys from modules - backtrace is re-loaded with some meaningful data
(In reply to Elena Laskavaia from comment #1) > I took a liberty of re-purposing this bug to actuly fix this action > rather then remove > > The main scenarios our customer want to support are the following: > > Case 1 startup: > - application has 200 shared libs (!) > - debugger startup takes forever with auto-solib > - we turn off auto-solib for this > - but now we want to load some stuff manually > > Case 2 attach: > > - we attach to application > - we stop at random place and our backtrace looks like bunch on binary > addresses > - we load some librarys from modules > - backtrace is re-loaded with some meaningful data BTW, the CDI implementation allowed users to turn off the auto-solib option and specify the list of libraries who's symbols they wanted to load at startup. I believe it was done by the request from the same customer :)
> > BTW, the CDI implementation allowed users to turn off the auto-solib option > and specify the list of libraries who's symbols they wanted to load at > startup. I believe it was done by the request from the same customer :) I checked this a while ago to figure out what this feature was doing and I don't think it is doing anything even in CDI anymore
(In reply to Elena Laskavaia from comment #3) > > > > BTW, the CDI implementation allowed users to turn off the auto-solib option > > and specify the list of libraries who's symbols they wanted to load at > > startup. I believe it was done by the request from the same customer :) > > I checked this a while ago to figure out what this feature was doing and I > don't think it is doing anything even in CDI anymore As far as I remember the main functionality including the UI was implemented in in the commercial product, only the core support was included into CDT. I may be wrong though.
(In reply to Mikhail Khodjaiants from comment #2) > BTW, the CDI implementation allowed users to turn off the auto-solib option That we have in DSF-GDB like CDI (using the launch tab Debugger->Shared Libraries) > and specify the list of libraries who's symbols they wanted to load at > startup. I believe it was done by the request from the same customer :) > As far as I remember the main functionality including the UI was implemented > in in the commercial product, only the core support was included into CDT. I > may be wrong though. I don't believe we have this part, which would make sense if it was not part of stock CDI.
Elena, can you put a note and screenshot in the N&N about this? Thanks! https://wiki.eclipse.org/CDT/User/NewIn86
Elena, are we done with this bug?
