From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20966@debbugs.gnu.org
Subject: bug#20966: 25.0.50; `button-at': (wrong-type-argument integer-or-marker-p nil), and *Backtrace* broken
Date: Sat, 30 Apr 2016 22:05:33 +0200 [thread overview]
Message-ID: <87d1p6c16a.fsf@gnus.org> (raw)
In-Reply-To: <3e1392be-1b72-4e03-85da-0ad1f4c3af03@default> (Drew Adams's message of "Thu, 2 Jul 2015 12:35:24 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Double regression, it seems. Perhaps this has been fixed since this
> build, but I cannot find a Windows binary that is more recent, so I
> can't get beyond this.
>
> 1. Non-nil debug-on-error gives a _completely empty *Backtrace* buffer_,
> except for the first line, which says "Debugger entered--Lisp error:
> (args-out-of-range 20324)". I've never seen that before, but I get it
> consistently with this build.
>
> 2. So I tried `M-x debug-on-entry describe-function-1', to see what
> went wrong. Here's a backtrace, from using `describe-function':
>
> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
> * get-char-property(nil button)
> * button-at(nil)
> * help-xref-button(1 help-function-def icicle-highlight-input-noncompletion=
> "d:/usr/drew/drews-lisp-20/icicles-fn.el")
Do you have a recipe to reproduce this bug?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-30 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 19:35 bug#20966: 25.0.50; `button-at': (wrong-type-argument integer-or-marker-p nil), and *Backtrace* broken Drew Adams
2015-07-02 22:13 ` Glenn Morris
2016-04-30 20:05 ` Lars Ingebrigtsen [this message]
2016-04-30 20:47 ` Drew Adams
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=87d1p6c16a.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20966@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).