From: David Reitter <david.reitter@gmail.com>
To: Lars Ingebrigtsen <larsi@mouse.gnus.org>
Cc: 3930-close@debbugs.gnu.org
Subject: bug#3930: DocView failure - bad error message, insufficient documentation
Date: Fri, 23 Aug 2019 07:20:19 -0400 [thread overview]
Message-ID: <F3C37FAD-0712-44D7-872A-B1C322A64681@gmail.com> (raw)
In-Reply-To: <87a7c0tvhj.fsf@mouse.gnus.org>
This works for me now.
> On Aug 22, 2019, at 11:24 PM, Lars Ingebrigtsen <larsi@mouse.gnus.org> wrote:
>
> David Reitter <david.reitter@gmail.com> writes:
>
>> Trying to open a PDF file with Emacs/NS 23.1 branch (actually
>> Aquamacs, which has no relevant patches compared to the 23.1 branch),
>> I keep getting a "DocView: process pdf/ps->png changed status to
>> trace/BPT trap." message in *Messages*.
>>
>> This happens with all PDFs, even small PDF files.
>>
>> The buffer that is shown is not updated to reflect the error status.
>>
>> What's worse is that the error message that is given is absolutely
>> unhelpful. It's unclear what "trace" or "BPT trap" means in this
>> concept, or what the abbreviation "BPT" is supposed to mean. This
>> does not help me as a user in addressing the error condition.
>
> (I'm going through old bug reports that unfortunately haven't gotten any
> responses yet.)
>
> The string "BPT trap" doesn't exist in the Emacs code base (at least not
> now), so I would suspect that it's an error message given by your OS?
>
> Are you still seeing this problem in more modern Emacs versions?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-08-23 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 6:08 bug#3930: DocView failure - bad error message, insufficient documentation David Reitter
2019-08-23 3:24 ` Lars Ingebrigtsen
2019-08-23 11:20 ` David Reitter [this message]
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=F3C37FAD-0712-44D7-872A-B1C322A64681@gmail.com \
--to=david.reitter@gmail.com \
--cc=3930-close@debbugs.gnu.org \
--cc=larsi@mouse.gnus.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).