Eli Zaretskii wrote:
> Yes, thanks. Unfortunately, it doesn't say more than the previous
> backtrace: Emacs is displaying some display string with invisible
> property. Why that would lead to an infloop, I don't see.
>
> My suggestion at this point would be to ask on the Org list whether
> your
> From: Fabrice Niessen
> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
> Date: Fri, 30 Jan 2015 17:07:13 +0100
>
> (gdb) thread 1
> [Switching to thread 1 (Thread 8340.0x2568)]
> #0 0x01101915 in XSTRING (a=168379948) at C:/emacs/repo/src/lisp.h:974
> (gdb) 974 C:/emacs/repo/src/lisp.h: No
Eli Zaretskii wrote:
>> From: Fabrice Niessen
>> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 13:04:00 +0100
>>
>> (gdb) thread 1
>> [Switching to thread 1 (Thread 17252.0x44f0)]
>> #0 0x01142191 in Fnext_single_property_change (position=position@entry=540,
>> prop=
> > Looks like an infloop due to display or overlay strings with text
> > properties. Can you reproduce this in an unoptimized build?
>
> Sure, if you can point me to such a version I can download.
https://sourceforge.net/projects/emacs-bin/files/snapshots/debug/
HTH
--
Dani Moncayo
The alternative is to supply a minimum reproducible recipe starting with
emacs -Q, then someone else can debug it.
BTW, it's a nice gesture to provide screencasts, but I don't think
anyone developing Emacs finds them particularly useful for debugging, so
no need to keep providing those AFAICS.
> From: Fabrice Niessen
> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 19:31:38 +0100
>
> > Looks like an infloop due to display or overlay strings with text
> > properties. Can you reproduce this in an unoptimized build?
>
> Sure, if you can point me to such a version
Fabrice Niessen writes:
> On Cygwin (I'm on Windows), that does not seem to work:
>
> kill -10
> kill -USR2
Cygwin kill only works with Cygwin processes, while your backtrace is
from a Windows Emacs. The problem of the incomplete traces might also
be related to your attempt to attach a Cygw
Eli Zaretskii wrote:>> From: Fabrice Niessen
>> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 13:04:00 +0100
>>
>> (gdb) thread 1
>> [Switching to thread 1 (Thread 17252.0x44f0)]
>> #0 0x01142191 in Fnext_single_property_change (position=position@entry=540,
>> prop=6
> From: Fabrice Niessen
> Cc: dgu...@yandex.ru, 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 13:04:00 +0100
>
> (gdb) thread 1
> [Switching to thread 1 (Thread 17252.0x44f0)]
> #0 0x01142191 in Fnext_single_property_change (position=position@entry=540,
> prop=62947906, object=118795585, l
Eli Zaretskii wrote:
>> From: Fabrice Niessen
>> Cc: 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 12:27:16 +0100
>>
>> OK, so I just reproduced the problem once again, then:
>>
>> - tried to C-g in Emacs: impossible!
>> - launched GDB
>> - source ~/.gdbinit
>> - thread 1
>> - thread apply all
Eli Zaretskii wrote:
>> From: Fabrice Niessen
>> Cc: 19...@debbugs.gnu.org
>> Date: Fri, 16 Jan 2015 12:16:26 +0100
>>
>> Eli Zaretskii wrote:
From: Glenn Morris
Cc: Fabrice Niessen , 19...@debbugs.gnu.org
Date: Thu, 15 Jan 2015 16:37:36 -0500
I just want to note that
> From: Fabrice Niessen
> Cc: 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 12:27:16 +0100
>
> OK, so I just reproduced the problem once again, then:
>
> - tried to C-g in Emacs: impossible!
> - launched GDB
> - source ~/.gdbinit
> - thread 1
> - thread apply all backtrace
>
> Still, the backt
> From: Fabrice Niessen
> Cc: 19...@debbugs.gnu.org
> Date: Fri, 16 Jan 2015 12:16:26 +0100
>
> Eli Zaretskii wrote:
> >> From: Glenn Morris
> >> Cc: Fabrice Niessen , 19...@debbugs.gnu.org
> >> Date: Thu, 15 Jan 2015 16:37:36 -0500
> >>
> >>
> >> I just want to note that there seems to be a
Eric Abrahamsen wrote:
> Fabrice Niessen writes:
>> Eli Zaretskii wrote:
From: Glenn Morris
Cc: Fabrice Niessen , 19...@debbugs.gnu.org
Date: Thu, 15 Jan 2015 16:37:36 -0500
I just want to note that there seems to be a tendency to try and
use gdb to debug Org proble
Fabrice Niessen wrote:
> OK, so I just reproduced the problem once again, then:
>
> - tried to C-g in Emacs: impossible!
> - launched GDB
> - source ~/.gdbinit
> - thread 1
> - thread apply all backtrace
>
> Still, the backtrace is not as long as normal, and I don't get any GDB
> prompt anymore!
>
Eli Zaretskii wrote:
>> Date: Fri, 16 Jan 2015 00:06:58 +0300
>> From: Dmitry Gutov
>> CC: 19...@debbugs.gnu.org
>>
>> On 01/15/2015 09:14 PM, Eli Zaretskii wrote:
>>
>>> But you didn't even show the backtrace from the main (a.k.a. "Lisp")
>>> thread. Your backtrace is from thread 15, whereas t
Fabrice Niessen
writes:
> Eli Zaretskii wrote:
>>> From: Glenn Morris
>>> Cc: Fabrice Niessen ,
>>> 19606-ubl+/3LiMTaZdePnXv/o...@public.gmane.org
>>> Date: Thu, 15 Jan 2015 16:37:36 -0500
>>>
>>>
>>> I just want to note that there seems to be a tendency to try and use
>>> gdb to debug Org p
Eli Zaretskii wrote:
>> From: Glenn Morris
>> Cc: Fabrice Niessen , 19...@debbugs.gnu.org
>> Date: Thu, 15 Jan 2015 16:37:36 -0500
>>
>>
>> I just want to note that there seems to be a tendency to try and use
>> gdb to debug Org problems, when debug-on-quit and ctrl-g might work.
>
> Very true.
> From: Glenn Morris
> Cc: Fabrice Niessen , 19...@debbugs.gnu.org
> Date: Thu, 15 Jan 2015 16:37:36 -0500
>
>
> I just want to note that there seems to be a tendency to try and use gdb
> to debug Org problems, when debug-on-quit and ctrl-g might work.
Very true.
> Date: Fri, 16 Jan 2015 00:06:58 +0300
> From: Dmitry Gutov
> CC: 19...@debbugs.gnu.org
>
> On 01/15/2015 09:14 PM, Eli Zaretskii wrote:
>
> > But you didn't even show the backtrace from the main (a.k.a. "Lisp")
> > thread. Your backtrace is from thread 15, whereas the main thread is
> > threa
I just want to note that there seems to be a tendency to try and use gdb
to debug Org problems, when debug-on-quit and ctrl-g might work.
On 01/15/2015 09:14 PM, Eli Zaretskii wrote:
But you didn't even show the backtrace from the main (a.k.a. "Lisp")
thread. Your backtrace is from thread 15, whereas the main thread is
thread 1.
The output is from 'thread apply all backtrace', AFAICS.
On the other hand, it's not 'bt full' or `
> From: Fabrice Niessen
> Cc: 19...@debbugs.gnu.org
> Date: Thu, 15 Jan 2015 19:04:13 +0100
>
> > Thanks, but what do you expect us to do with this report, without any
> > information whatsoever regarding your customizations?
>
> I thought that, thanks to the backtrace, you could find the culpri
Eli Zaretskii wrote:
>> From: Fabrice Niessen
>>
>> With the following file -- and my configuration file (!):
>>
>> --8<---cut here---start->8---
>> #+TITLE: ECM
>> #+LANGUAGE: en
>>
>> #+PROPERTY: eval yes
>>
>> * Macro
>>
>> Date at export time: /{{
24 matches
Mail list logo
