bug-gnu-emacs
[Top][All Lists]
Advanced

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

bug#34138: 27.0.50; Delayed display of PDF file images


From: Stephen Berman
Subject: bug#34138: 27.0.50; Delayed display of PDF file images
Date: Sun, 20 Jan 2019 18:14:13 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

On Sun, 20 Jan 2019 18:50:00 +0200 Eli Zaretskii <address@hidden> wrote:

>> From: Stephen Berman <address@hidden>
>> Cc: address@hidden, address@hidden, address@hidden,
>> address@hidden
>> Date: Sun, 20 Jan 2019 17:31:13 +0100
>> 
>> > Hmm... can you attach the debugger to Emacs during that delay, and
>> > show both C backtrace and Lisp backtrace?
>> 
>> I'm not sure what "attach the debugger to Emacs during that delay"
>> means
>
> It means, during the time of the delay, type from the shell prompt:
>
>   $ gdb -p PID
>
> where PID is the numeric process-id of the Emacs process; you should
> find that in advance, e.g. by running "ps".  Once GDB starts and shows
> its prompt, "(gdb)", type:
>
>   (gdb) thread apply all bt
>
> This should show the C-level backtrace.  Then:
>
>   (gdb) source /path/to/emacs/src/.gdbinit
>   (gdb) xbacktrace
>
> The last command should show the Lisp-level backtrace.

Ah, thanks.  I started gdb from the path of the emacs executable and the
Lisp backtrace was shown after typing "thread apply all bt";
subsequently typing xbacktrace showed no output.  Transcript attached.
FWIW, while the backtrace was being shown in the shell, the raw PDF
changed to the image display in Emacs.

Steve Berman

Attachment: txt7ACntct3MJ.txt
Description: gdb backtrace


reply via email to

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