I'm new to the language and new to using MonoDevelop and I've got this persistent problem that I haven't been able to solve with Google searching. I frequently test out my code as I write it and every time I start it up a new gdb process will start running but not terminate at the end of the program. Even a nothing program like the following will start up a new gdb process that won't terminate:

int main( string[] args ){
    return 0;
}

After testing out an application a few times I have to open my process manager and clear out one gdb for every time I ran the program. I'm using Linux Mint 17 x64.

Does anyone know how I can configure gdb to exit when a program has exited successfully?

i am assuming you are using the built in gdb debugger.

a) you can try using this addin Gdb.D instead -https://github.com/llucenic/MonoDevelop.Debugger.Gdb.D
it might be also be in the monodevelop beta repos.

b) you can "fix"/work around the issue by replacing "Syscall.kill" in the source (https://github.com/mono/monodevelop/blob/master/main/src/addins/MonoDevelop.Debugger.Gdb/GdbSession.cs)
with "proc.Kill()"
similarly as what was done in the Gdb.D source (https://github.com/llucenic/MonoDevelop.Debugger.Gdb.D/blob/master/Gdb/GdbSession.cs)
then recompile and use.

On Wednesday, 10 June 2015 at 20:46:11 UTC, Rodger Beats wrote:
> I'm new to the language and new to using MonoDevelop and I've got this persistent problem that I haven't been able to solve with Google searching. I frequently test out my code as I write it and every time I start it up a new gdb process will start running but not terminate at the end of the program. Even a nothing program like the following will start up a new gdb process that won't terminate:
>
> int main( string[] args ){
>     return 0;
> }
>
> After testing out an application a few times I have to open my process manager and clear out one gdb for every time I ran the program. I'm using Linux Mint 17 x64.
>
> Does anyone know how I can configure gdb to exit when a program has exited successfully?