GNU bug report logs - #20660
25.0.50; Window pops now issue "Args out of range" with popwin mode enabled

Previous Next

Full log

Message #22 received at 20660-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 20660-done <at> debbugs.gnu.org, Dmitry Gutov <dgutov <at> yandex.ru>,
 m2ym.pub <at> gmail.com, Kaushal <kaushal.modi <at> gmail.com>
Subject: Re: 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

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Kaushal <kaushal.modi <at> 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

Previous Next

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