emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs's set-frame-size can not work well with gnome-shell?


From: martin rudalics
Subject: Re: Emacs's set-frame-size can not work well with gnome-shell?
Date: Thu, 30 Jan 2020 19:04:32 +0100

>> around line 8927 in xterm.c and do "n" after that breakpoint is hit,
>> what do you get if you do p f now?
>
> So. Putting a breakpoint on that line gives me:
>
> Thread 1 "emacs" hit Breakpoint 4, handle_one_xevent (dpyinfo=0x555555fc5000,
>      event=0x7fffffffcbb0, finish=0x555555b9df30 <current_finish>, 
hold_quit=0x7fffffffce30)
>      at xterm.c:8923
> 8923          f = x_top_window_to_frame (dpyinfo, 
configureEvent.xconfigure.window);
> (gdb) p f
> $1 = (struct frame *) 0x0
> (gdb) print
> $2 = (struct frame *) 0x0
> (gdb) xframe
> $3 = (struct frame *) 0x0
> Cannot access memory at address 0x8
>
> but that probably makes sense, since the var has not been assigned yet.

That's why I said to do "n" after that breakpoint is hit ;-)

> Putting a breakpoint at the next statement gives me this:
>
> Thread 1 "emacs" hit Breakpoint 5, handle_one_xevent (dpyinfo=0x555555fc5000,
>      event=<optimized out>, finish=0x555555b9df30 <current_finish>, 
hold_quit=0x7fffffffce30)
>      at xterm.c:8929
> 8929          block_input ();
> (gdb) p f
> $4 = (struct frame *) 0x5555560a5aa0
> (gdb) xframe
> $5 = (struct frame *) 0x5555560a5aa0
> "test child-frame"

OK.  But no resizing after that ...

martin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]