GNU bug report logs -
#34179
27.0.50; message hangs when buffer with process visible
Previous Next
Reported by: Michael Heerdegen <michael_heerdegen <at> web.de>
Date: Wed, 23 Jan 2019 15:11:02 UTC
Severity: normal
Found in version 27.0.50
Fixed in version 27.1
Done: Noam Postavsky <npostavs <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: 34179 <at> debbugs.gnu.org
> Date: Thu, 24 Jan 2019 14:35:56 +0100
>
> I'll leave that session open. Does that all tell you anything? Again:
> this happens only when a *shell* buffer is currently displayed in some
> frame.
These seem just random places. What I suggest is to repeatedly type
"finish" at GDB prompt, until you find a function where this command
takes a lot of time before GDB displays its prompt "(gdb)" again. At
that point, the function from which you just "finish"ed is the one
that takes the bulk of time; GDB should have displayed it when you
typed "finish", something like this:
(gdb) finish
Run till exit from #0 Fredraw_display () at dispnew.c:3031 <<<<<<<<<<<<<<<
0x0123a014 in funcall_subr (subr=0x16c7040 <Sredraw_display>, numargs=0,
args=0x82d8c0) at eval.c:2933
(gdb)
Here the marked line is our culprit, and the line below that shows the
place from which it was called.
This bug report was last modified 6 years and 54 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.