On Mon, May 16, 2016 Ken Moffat wrote: >> I have difficulty with it - usually, the problems are in C++ desktop >> applications which do not work correctly. If a c++ batch (whoops, >> showing my background, let me try again) ... If a C non-graphical >> program segfaults, I might be able to get a sensible backtrace. > > s/c++ batch/C batch/ : debugging and c++ is hard.
I've been using CodeLite ( http://www.codelite.org/ ) and it's Quick Debug menu option for debugging a lot lately. I thought it was pretty easy (at least compared to printf or cout statements in the code for debugging). Then again, I'm a C/C++ programmer. I've tried to use gdb with its tui (text user interface), but didn't find it too intuitive to work with. I've also looked at some other simple GNU debugger GUIs, but haven't had much luck with them. Maybe someone else has found a user friendly, lightweight, low dependency GUI for gdb? There's a debugger addon for SciTE ( http://scitedebug.luaforge.net/ ) that I've tried out. It's okay, but the CodeLite interface seems more user friendly. Although, I do prefer SciTE for source code editing. Tried building rhide (ncurses/turbovision interface), but it's not going to be easy to update the code for latest versions of gdb. I was also looking into getting the gdb code working for fldev ( https://sourceforge.net/projects/fldev/ ), but haven't really had much time to work on it. gdbwire ( https://github.com/brasko/gdbwire ) looked interesting, but couldn't find any GUI front ends currently using it. Setedit (similar to rhide) uses libmigdb to communicate with gdb. So far, CodeLite has been the easiest option to use that is also not too involved to build from source. Other alternatives would be nice though. Sincerely, Laura -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
