I have a rather complex OpenGL, fltk, gdal, multi threaded c++ app. Which crashes gdb when I break in the OpenGL thread and then continue. I can switch to command line gdb and debug without problems but that is so painfully slow in comparison to eclipse.
Do I need to get a simple app that had a similar problem to proceed from here. Or does anyone have any good advice...
Start GDB manually like this:
<gdbPath> -interpreter mi -nx
Then copy/paste the commands one by one, and reproduce the crash. After that, I normally trip the set of commands until I find a small sequence that causes the crash. Then you can report it to the GDB community.
i got a bit further, if i cut and paste the multi-line cmds into gedit and edit it back to a single line cmd it works, but when i get to "13-exec-run" my app terminates saying /dev/pts/1: No such file or directory - the previous gdb cmd was "12-inferior-tty-set /dev/pts/1"
interestingly, when eclipse loses contact with my app - there is a long pause - then after the terminated -1 message in the Debug/call stack pane, the app is left running, then if i try and load a file or interact with the app in any way it will shut down.
Sorry, you should skip the "12-inferior-tty-set /dev/pts/1".
/dev/pts/1 was created by eclipse, so when you copy/paste it again, it won't exist.
Just skip that command and see if you can see what else makes it fail.