From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Kaushal <kaushal.modi@gmail.com>,
20660-done@debbugs.gnu.org, m2ym.pub@gmail.com,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#20660: 25.0.50; Window pops now issue "Args out of range" with popwin mode enabled
Date: Mon, 30 Sep 2019 01:50:32 +0200 [thread overview]
Message-ID: <CADwFkmmXwF+fW+oPKKbJqohV_K6SnjqE6F5G1ZTMuhMGX0BmEw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY0sOoV1XPS0fy8WNRfQ_vqJcEm_69ukTU=O38KdNutNHg@mail.gmail.com>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Kaushal <kaushal.modi@gmail.com>
>> Date: Thu, 11 Jun 2015 15:10:44 +0000
>>
>> Any hints on how I can debug this more?
>
> I'm not Dmitry, but I will give advice nonetheless.
>
> Try running Emacs under GDB, setting a breakpoint in the function
> named args_out_of_range. When it breaks, the command "xbacktrace"
> (defined in src/.gdbinit) will display a Lisp-level backtrace, whuch
> might give you enough hints to find the culprit. If not, the command
> "backtrace" will show a C-level backtrace; post it here if you cannot
> figure it out.
>
> If the breakpoint in args_out_of_range breaks too much in situations
> not related to your problem, you can make the breakpoint continue the
> execution automatically:
>
> (gdb) break args_out_of_range
> (gdb) commands
> > xbacktrace
> > continue
> >end
>
> Then only look at the output of GDB when you see the problem
> happening.
This seems to be an error related to a third party package, and there
have been no further update in 4 years. I'm therefore closing this
bug. If this is indeed a bug in Emacs, please ropen.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-09-29 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 14:31 bug#20660: 25.0.50; Window pops now issue "Args out of range" with popwin mode enabled Kaushal
2015-05-26 14:38 ` Dmitry Gutov
2015-05-26 17:03 ` Kaushal
2015-06-11 15:10 ` Kaushal
2015-06-11 15:56 ` Eli Zaretskii
2019-09-29 23:50 ` Stefan Kangas [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=CADwFkmmXwF+fW+oPKKbJqohV_K6SnjqE6F5G1ZTMuhMGX0BmEw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=20660-done@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=m2ym.pub@gmail.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).