Subject: bug#30964: python-mode failing "overlapping strings" assertion lately

From: Andreas Röhler <[email-masked]>
Date: Sat, 19 May 2018 08:49:40 +0200

On 19.05.2018 03:49, Noam Postavsky wrote:
> Andreas Röhler <[email-masked]> writes:
> 
>> On 18.05.2018 17:46, Clément Pit-Claudel wrote:
>>
>>> This error triggers in the wild for me due to which-function-mode, which calls python-info-current-defun.
>>>
>>> Clément.
>>>
>>>
>>>
>>
>> Can't reproduce with GNU Emacs 26.1 (build 1, i686-pc-linux-gnu, GTK+
>> Version 3.14.5) of 2018-04-10
> 
> I can reproduce, if and only if I make sure to put a newline on the last
> line.
> 

Okay, got the error at some point when inserting a newline. However a 
newline must not trigger it - see attachment.

Below some reports which might be of interest:

Which-Function mode enabled
next-line: End of buffer
Which-Function mode disabled
next-line: End of bufferError during redisplay: (jit-lock-function 3905) 
signaled (error "Overlapping strings detected")
Error during redisplay: (jit-lock-function 3905) signaled (error 
"Overlapping strings detected")
Which-Function mode enabled
Error during redisplay: (jit-lock-function 3919) signaled (error 
"Overlapping strings detected") [2 times]
Which-Function mode disabled
Error during redisplay: (jit-lock-function 3905) signaled (error 
"Overlapping strings detected") [2 times]
Which-Function mode enabled
C-c e is undefined
M-+ is undefined
C-x c is undefined
Which-Function mode disabled
Which-Function mode enabled
Mark set [4 times]
scroll-up-command: End of buffer
Mark set [2 times]
Saved text from "Which-Function mode disabled
next-line: "
Auto-saving...
Mark set [2 times]