Re: Using gdb (windows popping up)

[Óscar Fuentes]

jonetsu <jonetsu@teksavvy.com> writes:

> On Sun, 9 Jun 2019 12:18:23 -0400
> jonetsu <jonetsu@teksavvy.com> wrote:
>
>> ... Until the debugged app outputs something.  Then yes, the problem
>> with a new emacs instance popping is solved, but emacs insists on
>> replacing the source code with the output window.  
>
> Found out that this is solved by setting the following variable to
> non-nil (default is nil) :
>
> gdb-display-io-nopopup
>
> Also saw that there are incredible people with lots of patience, as
> this Stack Exchange post on this topic shows, with the subject:
>
> "How can I prevent gdb *input/output* buffer from aggressively popping
> up in frame?"
>
> The above solution is presented and the reply was:
>
> "Thank you, thank you, thank you! This has been an irritation for me for
> years!"
>
> I mean, years ?  I couldn't stand it for a day ! :)

Due to this issues with windows and frames popping out, I don't use
Emacs' gdb interface, but will give it another chance with this trick
next time, thanks.

Please use M-x report-emacs-bug to report about this issues to the Emacs
maintainers and mention your workaround.