From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: stack overflow in regexp matcher with gdb Date: Wed, 13 Nov 2013 14:06:24 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1384369633 31707 80.91.229.3 (13 Nov 2013 19:07:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Nov 2013 19:07:13 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Nov 13 20:07:16 2013 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VgfmR-0003JU-EK for geh-help-gnu-emacs@m.gmane.org; Wed, 13 Nov 2013 20:07:11 +0100 Original-Received: from localhost ([::1]:50319 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgfmQ-0002zH-T0 for geh-help-gnu-emacs@m.gmane.org; Wed, 13 Nov 2013 14:07:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35740) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vgfm2-0002qa-NV for help-gnu-emacs@gnu.org; Wed, 13 Nov 2013 14:06:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vgflv-00010l-Dl for help-gnu-emacs@gnu.org; Wed, 13 Nov 2013 14:06:46 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:50885) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vgflv-00010Y-7M for help-gnu-emacs@gnu.org; Wed, 13 Nov 2013 14:06:39 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vgflt-0002cZ-Ur for help-gnu-emacs@gnu.org; Wed, 13 Nov 2013 20:06:37 +0100 Original-Received: from 108.175.230.244 ([108.175.230.244]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 13 Nov 2013 20:06:37 +0100 Original-Received: from monnier by 108.175.230.244 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 13 Nov 2013 20:06:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 108.175.230.244 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:xcsiuBsa6ASXq8TS/TXfP3ctl+I= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:94481 Archived-At: > error in process filter: gdb-stack-list-locals-handler: Stack overflow in regexp matcher > error in process filter: Stack overflow in regexp matcher Please try to enable "Options => Enter Debugger on Error", and if that fails to give you a backtrace, then try M-: (setq debug-on-signal t) RET [ But note that this latter option will make your Emacs session "inconvenient" because the debugger will be triggered too often. ] That should hopefully give you a backtrace which can help fix the problem. Of course, M-x report-emacs-bug is also a good idea. In any case, you'll probably want to try Emacs-24.3 first, to see if this bug hasn't been fixed already. > I don't know where it comes from, I've been searching on the web and > found a bug report was entered some years ago but it seems it ended here. It means that the backtracking-based regexp-matcher recursed too deep (probably because some "*" repetition matched many more times than normally expected). The best fix usually is to change the regexp so it backtracks less (i.e. uses less stack space) or so the match fails much earlier. > Is there any way to turn that thing off (whatever it is doing) so I can at > least continue debugging in a normal way ? Not sure: using M-x gud-gdb RET instead of M-x gdb would be a way, but that requires re-starting the GDB session (and it gives you a much more barebones UI, tho that's what I use personally). Stefan