Community
Participate
Working Groups
Build Identifier: Version: Helios Service Release 1 Build id: 20100917-0705 1) When debugging an elf-file and the first breakpoint in main is hit I set a breakpoint in another c-file and hit "resume" the program never continues running although it should. 2) Then, if I "terminate and remove" the debug session and start a new one. The previously set breakpoints have the following error message: "Breakpoint attribute problem: installation failed" The elf-program never starts and the only way to start the elf program is to remove the breakpoints and restart the elf-program. 3) Also, if I have any breakpoint set in some other file, and then start a debug of the elf-program, the "main" breakpoint is never reached. It seems as if the program never starts. Reproducible: Always Steps to Reproduce: 1. Start Eclipse/CDT 2. Debug an elf-program 3. When the elf-program has stopped on the "main" breakpoint, set another breakpoint in some other c-file. Hit "Resume (F8)". Now the elf-program should continue running but it doesn't.
Hi, In the console view where the mi commands are sent by Eclipse to gdb I can see that when the problem occurs, no mi commands are sent by Eclipse. I.e., if I set or remove a breakpoint in any other c-file than the one containing main, the corresponding mi command can not be seen in the console view (I have pinned the console view). Brs, Markus
Hi, I noticed that setting breakpoints via the gdb console in Eclipse works, but using the gui, i.e. right clicking and setting the breakpoint, doesn't work. Brs, Markus
Hi, I think I got same problem: I am working with Eclipse SDK (Version: 3.7.2) - CodeSourcery and Stlink to STM32F4; running on Ubuntu 11.04. I am able to debug. I just have problems when working with breakpoints. I can insert them, but they are not recognized. I mean, when doing resume, execution does not stop on them. By the way, when loading Debug file I get next warning: "Warning: RMT ERROR: failed to get remote thread list". Then, I start debugging. When inserting breakpoint, appears: "Breakpoint attribute problem: installation failed". Binary file seems to be well done. I think could be a problem on configuring debugger parameters. Surfing by the net I saw someone within same problem, saying it is resolved by updating gcc-ubuntu to 7.2. Nevertheless, I am working with arm-none-eabi-gdb version 7.2.50 which is the last one at this time. Others said gdb was not well configured on Eclipse, I checked it, this is not my case. Lot of topics on the net about this, no solution available.
(In reply to comment #3) > Hi, > I think I got same problem: > I am working with Eclipse SDK (Version: 3.7.2) - CodeSourcery and Stlink to > STM32F4; running on Ubuntu 11.04. > I am able to debug. I just have problems when working with breakpoints. I can > insert them, but they are not recognized. I mean, when doing resume, execution > does not stop on them. > By the way, when loading Debug file I get next warning: > "Warning: RMT ERROR: failed to get remote thread list". That is probably not good... > Then, I start debugging. When inserting breakpoint, appears: > "Breakpoint attribute problem: installation failed". Can you attach the 'gdb traces' so we can see what the error is? http://wiki.eclipse.org/CDT/User/FAQ#I.27ve_been_asked_for_.27gdb_traces.27.2C_where_can_I_find_them.3F
(In reply to comment #4) > (In reply to comment #3) > > Hi, > > I think I got same problem: > > I am working with Eclipse SDK (Version: 3.7.2) - CodeSourcery and Stlink to > > STM32F4; running on Ubuntu 11.04. > > I am able to debug. I just have problems when working with breakpoints. I can > > insert them, but they are not recognized. I mean, when doing resume, execution > > does not stop on them. > > By the way, when loading Debug file I get next warning: > > "Warning: RMT ERROR: failed to get remote thread list". > > That is probably not good... > > > Then, I start debugging. When inserting breakpoint, appears: > > "Breakpoint attribute problem: installation failed". > > Can you attach the 'gdb traces' so we can see what the error is? > http://wiki.eclipse.org/CDT/User/FAQ#I.27ve_been_asked_for_.27gdb_traces.27.2C_where_can_I_find_them.3F Hi again, After lot of tests, I realize RMT ERROR disappear also when using Standard GDB Hardware Debuging. Then, I think this could also be a bug on DSF HW Debuging. Now, with standard GDB, it works pretty ok. :) Thks a lot for your help. Cheers, Pablo
