From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: emacs 25 broken? Date: Tue, 24 Feb 2015 15:15:00 -0600 Message-ID: <85oaojc8q3.fsf@stephe-leake.org> References: <85wq37cidj.fsf@stephe-leake.org> <83h9ub6vm5.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1424812562 8986 80.91.229.3 (24 Feb 2015 21:16:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Feb 2015 21:16:02 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 24 22:15:48 2015 Return-path: Envelope-to: ged-emacs-devel@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 1YQMpX-0001Jv-GC for ged-emacs-devel@m.gmane.org; Tue, 24 Feb 2015 22:15:47 +0100 Original-Received: from localhost ([::1]:51436 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQMpW-0004l6-OA for ged-emacs-devel@m.gmane.org; Tue, 24 Feb 2015 16:15:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40882) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQMpS-0004jw-KW for emacs-devel@gnu.org; Tue, 24 Feb 2015 16:15:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YQMpO-0000r5-J5 for emacs-devel@gnu.org; Tue, 24 Feb 2015 16:15:42 -0500 Original-Received: from gproxy2-pub.mail.unifiedlayer.com ([69.89.18.3]:52978) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1YQMpO-0000qO-74 for emacs-devel@gnu.org; Tue, 24 Feb 2015 16:15:38 -0500 Original-Received: (qmail 8713 invoked by uid 0); 24 Feb 2015 21:15:35 -0000 Original-Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy2.mail.unifiedlayer.com with SMTP; 24 Feb 2015 21:15:35 -0000 Original-Received: from host114.hostmonster.com ([74.220.207.114]) by cmgw4 with id wUF81p00D2UdiVW01UFBiv; Tue, 24 Feb 2015 21:15:14 -0700 X-Authority-Analysis: v=2.1 cv=GubRpCFC c=1 sm=1 tr=0 a=CQdxDb2CKd3SRg4I0/XZPQ==:117 a=CQdxDb2CKd3SRg4I0/XZPQ==:17 a=DsvgjBjRAAAA:8 a=f5113yIGAAAA:8 a=TeMFXEv2S7AA:10 a=9i_RQKNPAAAA:8 a=hEr_IkYJT6EA:10 a=jrwKn-8xaegA:10 a=0HtSIViG9nkA:10 a=mDV3o1hIAAAA:8 a=zXKpur76LUr9QyNLopEA:9 Original-Received: from [70.94.38.149] (port=50829 helo=takver) by host114.hostmonster.com with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.82) (envelope-from ) id 1YQMov-0008Au-Uq for emacs-devel@gnu.org; Tue, 24 Feb 2015 14:15:10 -0700 In-Reply-To: <83h9ub6vm5.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Feb 2015 19:57:06 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (windows-nt) X-Identified-User: {2442:host114.hostmonster.com:stephele:stephe-leake.org} {sentby:smtp auth 70.94.38.149 authed with stephen_leake@stephe-leake.org} X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 69.89.18.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:183466 Archived-At: Eli Zaretskii writes: >> From: Stephen Leake >> Date: Tue, 24 Feb 2015 11:46:32 -0600 >> >> Whenever I try to use emacs 25, something doesn't work right, and when >> trying to debug it I always run into bug #19611; "e (current-buffer)" in >> edebug returns the wrong buffer. >> >> Does anyone else see this problem? It's blocking all my work on master. > > Why do you need "e (current-buffer)" in Edebug so badly that it blocks > your work? Seriously? If I can't trust the debugger, how am I supposed to make progress? The real bug (in ada-mode) I'm trying to fix is in code that switches buffers. (That bug does not exist when the same code is run in emacs 24). Any expression I evaluate that relies on the current buffer is wrong in the debugger, so it's impossible to figure out what's going on. I did not record in the bug that `with-current-buffer' is not broken; executing M-x sal-debug gives the correct results. Any suggestions for further investigation? -- -- Stephe