From: "Ivor Durham" <ivor.durham@ivor.cc>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 24707@debbugs.gnu.org
Subject: bug#24707: 25.1; Window shrinks automatically after opening at normal size
Date: Mon, 31 Oct 2016 09:39:49 -0700 [thread overview]
Message-ID: <34277.3577002392$1505294182@news.gmane.org> (raw)
In-Reply-To: <83pommubyy.fsf@gnu.org>
I used "git clone git://git.savannah.gnu.org/emacs.git" to clone and build
emacs which produced version 26.0.50.1. I used the following command to
configure it to get past some missing packages:
./configure --without-makeinfo --with-xpm=no --with-gif=no --with-gnutls=no
Running src/emacs -Q and src/emacs -q (shows the logo graphic) without doing
a full install both work as expected without resizing the window.
How do I fetch the 25.1 sources to try to reproduce & debug the problem with
the same version that is actually exhibiting the problem?
-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org]
Sent: Wednesday, October 26, 2016 12:50 PM
To: Ivor Durham
Cc: rgm@gnu.org; 24707@debbugs.gnu.org
Subject: Re: bug#24707: 25.1; Window shrinks automatically after opening at
normal size
> From: "Ivor Durham" <ivor.durham@ivor.cc>
> Cc: <rgm@gnu.org>,
> <24707@debbugs.gnu.org>
> Date: Wed, 26 Oct 2016 12:30:21 -0700
>
> So I can think of a couple of ways to try to diagnose this:
> - Enable telnet into the workstation and use it instead of ssh so I
> can capture unencrypted network traffic with Wireshark to see if the X
> protocol communication reveals anything unusual.
> - Try to build a debugging version of Emacs 25.1 locally, reproduce
> the problem and then use gdb to break on whatever resize calls there
> are to find what parameters are being passed and where they come from.
> I know nothing about the Emacs implementation so this could be a bit of a
time sink.
>
> Any other ideas on how I should approach this?
The second approach is IMO the right one. I think if you put a breakpoint
in adjust_frame_size, you will see all the resizes.
next prev parent reply other threads:[~2016-10-31 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 7:27 bug#24707: 25.1; Window shrinks automatically after opening at normal size Ivor Durham
2016-10-16 18:00 ` Eli Zaretskii
[not found] ` <012901d227dd$26d5fee0$7481fca0$@durham@ivor.cc>
2016-10-16 19:09 ` Eli Zaretskii
2016-10-16 19:34 ` Ivor Durham
2016-10-25 19:43 ` Ivor Durham
[not found] ` <0b8a01d22ef8$15455c80$3fd01580$@durham@ivor.cc>
2016-10-25 23:06 ` Glenn Morris
2016-10-26 8:22 ` Ivor Durham
[not found] ` <0c1a01d22f62$0bfce7f0$23f6b7d0$@durham@ivor.cc>
2016-10-26 12:02 ` Eli Zaretskii
2016-10-26 17:06 ` Ivor Durham
[not found] ` <0cbd01d22fab$429aa5b0$c7cff110$@durham@ivor.cc>
2016-10-26 18:30 ` Eli Zaretskii
2016-10-26 19:30 ` Ivor Durham
[not found] ` <0cf201d22fbf$64b861f0$2e2925d0$@durham@ivor.cc>
2016-10-26 19:49 ` Eli Zaretskii
2016-10-31 16:39 ` Ivor Durham [this message]
[not found] ` <01ca01d23395$65f51570$31df4050$@durham@ivor.cc>
2016-10-31 20:43 ` Eli Zaretskii
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='34277.3577002392$1505294182@news.gmane.org' \
--to=ivor.durham@ivor.cc \
--cc=24707@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).