Eclipse Community Forums: C / C++ IDE (CDT) » "Breakpoint attribute problem: installation failed"

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » "Breakpoint attribute problem: installation failed"

Show: Today's Messages :: Show Polls :: Message Navigator

"Breakpoint attribute problem: installation failed" [message #643035]

Fri, 03 December 2010 17:36

Markus

Messages: 21
Registered: February 2010

Junior Member

Hi,

When I set breakpoints in Eclipse/CDT (Helios) I get the following error:
"Breakpoint attribute problem: installation failed"

Does anyone know how to resolve this?

Brs,
Markus

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #643234 is a reply to message #643035]

Mon, 06 December 2010 08:20

Axel Mueller

Messages: 1973
Registered: July 2009

Senior Member

This messages indicates that the source file where you set the breakpoint does not belong to the actual binary you are debugging (btw, gdb will issue this message). This can be the case if you have multiple binaries in your project that share the same source but not all of the files. You can ignore then this warning.

Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #643277 is a reply to message #643035]

Mon, 06 December 2010 11:18

Markus

Messages: 21
Registered: February 2010

Junior Member

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

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #643526 is a reply to message #643277]

Tue, 07 December 2010 09:27

Axel Mueller

Messages: 1973
Registered: July 2009

Senior Member

Markus wrote on Mon, 06 December 2010 12:18

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

You can activate gdb traces to see the gdb command input/output. Windows->Preferences-C/C++->Debug->gdb->Enable traces

Does the warning disappear when you actually run your program? Does it stop at the breakpoint set using the GUI?

Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #656751 is a reply to message #643277]

Mon, 28 February 2011 12:50

hefeweizen

Messages: 32
Registered: July 2009

Member

it does not make sense that one can not use the GUI in eclipse. If I want to use gdb directly, then I forget about eclipse

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #657028 is a reply to message #656751]

Tue, 01 March 2011 11:57

Axel Mueller

Messages: 1973
Registered: July 2009

Senior Member

hefeweizen wrote on Mon, 28 February 2011 13:50

it does not make sense that one can not use the GUI in eclipse. If I want to use gdb directly, then I forget about eclipse

Thanks a lot for your glorious comment. It will help the initial poster a lot.

Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #657035 is a reply to message #657028]

Tue, 01 March 2011 12:18

hefeweizen

Messages: 32
Registered: July 2009

Member

I am sorry about that, was not intended. I just felt bad that after a lot of testing, one of the most beautiful (in my opinion) programming IDEs can not use breakpoints while debugging. Any other IDE can do this: Visual Studio. Netbeans, Xcode, Bloodshed, etc

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #713917 is a reply to message #643035]

Tue, 09 August 2011 11:29

Daniel err

Messages: 1
Registered: August 2011

Junior Member

I often had the same problem.
I recently found that it was because an other occurence of my binary was not properly terminated. This can be view in the "debug perspective" where multiple C/C++ applications are still running (not marked as "Terminated")
You just have to select those and delete them.
Regards

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #717123 is a reply to message #713917]

Fri, 19 August 2011 11:26

Daniel

Messages: 2
Registered: August 2011

Junior Member

Hi!

I'm confused about the sentence "This can be view in the "debug perspective" where multiple C/C++ applications are still running (not marked as "Terminated") You just have to select those and delete them." In the "debug perspective" i didn't find the c/c++ applications list?

Thanks a lot!

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #717393 is a reply to message #713917]

Sat, 20 August 2011 11:01

Daniel

Messages: 2
Registered: August 2011

Junior Member

Got it!

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #1608366 is a reply to message #643035]

Mon, 09 February 2015 13:11

Serge Rogatch

Messages: 1
Registered: February 2015

Junior Member

I encountered this problem when trying to debug a 64-bit application. A workaround is to go to "Run" -> "Debug Configurations..." -> YOUR_CONFIGURATION -> tab "Debugge" -> check "Stop on startup at: main"

Report message to a moderator

Re: "Breakpoint attribute problem: installation failed" [message #1632901 is a reply to message #1608366]

Tue, 24 February 2015 14:56

Derek Lemon

Messages: 1
Registered: February 2015

Junior Member

This problem may also be encountered if your source paths or source lookup doesn't match up right.

For example if you are attaching to a program built on another machine, and the debugger is attempting to load all of the symbols by absolute path, your source location much match the build machines.

I know is a problem that I have ran into, I have just made my paths align which is probably the hard solution. GDB will resolve this just fine, but breakpoints in eclipse will fail.

I think this is most applicable when debugging with Attach to Application. There are other source lookup mechanisms you can use in the debug configuration underneath the source tab.

Report message to a moderator