Community
Participate
Working Groups
When doing remote-attach debugging, each time the user selects a process to attach to, she is prompted for the path of the binary on the host. It would be nice if we could remember the path of binaries so we could re-use them automatically. This is the scenario I see: the user does the remote connect and choose a proc called myProc to attach to. They get a file prompt and select a binary located at /myPath/myBinary. They detach from the process (to debug another process, or to go to lunch, or whatever). They come back and start a new session and again try to attach to 'myProc'. We would prompt them again for the path. I'm thinking that the odds are high that 'myProc' uses the same location for the binary as the first time it was debugged. We could automatically choose the binary, by remember the previous user choices. However, because we cannot guarantee that we are right in making that automatic choice, the user would need a way to intervene in this automatic decision. I'm thinking of a list of 'remembered binaries' that the user could edit from the preference page. The user could add paths before debugging to make things even easier. One thing that might affect this is the new 'Global breakpoints' feature, which allows us to give GDB a set of paths where binaries can be found. Once that is possible, we would not need to prompt for the binary, and this bug would not be necessary. I won't do anything just yet.
