unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36505@debbugs.gnu.org
Subject: bug#36505: 26.1; GDB stepping through code splits GUD windows
Date: Wed, 10 Jul 2019 09:13:53 -0600	[thread overview]
Message-ID: <a9a883d8-309b-39ff-0fa6-ec991b06b4b4@gmail.com> (raw)
In-Reply-To: <8336jlaueg.fsf@gnu.org>

On 7/5/19 12:05 AM, Eli Zaretskii wrote:
>> From: Martin Sebor <msebor@gmail.com>
>> Date: Thu, 4 Jul 2019 13:55:50 -0600
>>
>> Since the latest Fedora 29 update, while using the GUD many windows mode
>> and stepping in GDB into functions defined in other files than the
>> current one, Emacs will sometimes open the new file either by splitting
>> the current window, or sometimes in the input/output of gcc window.
>> Sometimes it seemingly abitrarily also resizes the windows and changes
>> the layout of the debugging session.  This makes debugging using GUD so
>> confusing that it's nearly unusable.  I end up using gdb-restore-windows
>> every few seconds to at least temporarily restore some sanity to the
>> layout.  Since the default layout isn't ideal for my use, I then have to
>> resize it to my preferred size only to have GUD screw it up again once I
>> step into a function in some other file.
> 
> Thanks, but could you please post a reproducible recipe starting from
> "emacs -Q" to exhibit the problem?  That would make looking into and
> fixing this problem much easier and more efficient.
> 
> I suspect the problem happens for certain frame and window dimensions,
> perhaps only when the frame in which you use gdb-mi is maximized?  But
> that's just a guess, and it would be good to have a recipe on which to
> work.

I am trying to reproduce it in a small test case but I'm all of
a sudden having trouble.  What's happening instead is that syntax
highlighting and indentation don't work in in some regions of code
but they work in others.  All the problems, including the window
resizing and files popping open in dedicated windows feel like they
have something to do with custom faces.  My setting is below.
Changing the font seems to have an effect (I'm just not sure
exactly what it is for which font).

My GUD frame isn't maximized.  Its geometry is set to 164x94 in
.Xresources.  My display is 3840x2160 in case that matters, and
my window manager is Cinnamon.

I'll keep trying to narrow it down to something more specific.

(custom-set-faces
  ;; custom-set-faces was added by Custom.
  ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.
  '(default ((t (:inherit nil :stipple nil :background "cornsilk" 
:foreground "black" :inverse-video nil :box nil :strike-through nil 
:overline nil :underline nil :slant normal :weight normal :height 143 
:width normal :foundry "PfEd" :family "DejaVu Sans Mono"))))
  '(font-lock-builtin-face ((((class color) (background light)) (:bold t 
:foreground "NavyBlue"))))
  '(font-lock-comment-face ((((class color) (background light)) 
(:foreground "SteelBlue"))))
  '(font-lock-constant-face ((((class color) (background light)) 
(:foreground "Black"))))
  '(font-lock-keyword-face ((((class color) (background light)) (:bold t 
:foreground "NavyBlue"))))
  '(font-lock-string-face ((((class color) (background light)) 
(:foreground "SeaGreen"))))
  '(font-lock-type-face ((((class color) (background light)) (:bold t 
:foreground "NavyBlue"))))
  '(font-lock-variable-name-face ((((class color) (background light)) 
(:bold nil :foreground "Black"))))
  '(region ((((class color) (background light)) (:background "lightcyan"))))
  '(scroll-bar ((t (:background "grey75")))))





  parent reply	other threads:[~2019-07-10 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 19:55 bug#36505: 26.1; GDB stepping through code splits GUD windows Martin Sebor
     [not found] ` <8336jlaueg.fsf@gnu.org>
2019-07-10 15:13   ` Martin Sebor [this message]
2019-07-10 15:55     ` Eli Zaretskii
2019-09-25 14:39       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9a883d8-309b-39ff-0fa6-ec991b06b4b4@gmail.com \
    --to=msebor@gmail.com \
    --cc=36505@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).