Community
Participate
Working Groups
Using CDT 8.8.0.201508011003 When I create an "Attach to Application" launch, I always have to select the "Disable auto build" option because it doesn't make sense to build as I am about to debug a running process that was already built. This is similar to bug 188116.
The delegates should just not do the build, ui settings should not be even visible
My main concern is attaching to the application cold, i.e., without having done a build, or with old build output and having the symbols mismatch. The debugger would be pretty confused.
(In reply to Doug Schaefer from comment #2) > My main concern is attaching to the application cold, i.e., without having > done a build, or with old build output and having the symbols mismatch. The > debugger would be pretty confused. I'm not sure I understand. If you attach it means the application is already running, you don't want to build a new binary and load possibly mismatching symbols compared to what's currently running. Right?
(In reply to Elena Laskavaia from comment #1) > The delegates should just not do the build, ui settings should not be even > visible Just having the delegate do nothing would be the simplest but ideally yes, the UI should not be visible.
I'm talking about the case where the executable that's running isn't the same one that's in the workspace that gdb uses to load the symbols. This is especially true with remote debugging on embedded devices. Ideally, the delegate is smart enough to check and do a build if necessary. Mind you, in those cases you may not even have the right version of the source checked out, so it's not foolproof by any means. I'm just truing to make sure we understand the consequences of this change because, there are some :).
