GNU bug report logs - #34138
27.0.50; Delayed display of PDF file images

Previous Next

Full log

Message #41 received at 34138 <at> debbugs.gnu.org (full text, mbox):

From: Stephen Berman <stephen.berman <at> gmx.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rudalics <at> gmx.at, 34138 <at> debbugs.gnu.org, politza <at> hochschule-trier.de,
 tsdh <at> gnu.org
Subject: Re: bug#34138: 27.0.50; Delayed display of PDF file images
Date: Sun, 20 Jan 2019 18:14:13 +0100

[Message part 1 (text/plain, inline)]

On Sun, 20 Jan 2019 18:50:00 +0200 Eli Zaretskii <eliz <at> gnu.org> wrote:

>> From: Stephen Berman <stephen.berman <at> gmx.net>
>> Cc: rudalics <at> gmx.at, 34138 <at> debbugs.gnu.org, politza <at> hochschule-trier.de,
>> tsdh <at> gnu.org
>> 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

[Message part 2 (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.