I had this 'bug' as well. Looking better at the output of the configure script I saw that some symbols were missing, especially AM_PROG_LIBTOOL. Looking this up on the web it appeared that I did not install libtool. After installing libtool the breakpoints do seem to work properly.
This is quite annoying for users that start using kdevelop for the first time and have no or little experience with automake and friends, because they will oversee this installation error: everything looks like it works fine, the errormessage is scrolled out of view very fast, and configure ends with "*** Sucess ***". I suggest setting breakpoints in Kdevelop without the possibility of using them should result in an error message in the messages window like: "libtool not found ==> breakpoint not effective". -- breakpoints do not work in kdevelop https://bugs.launchpad.net/bugs/243567 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
