emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#12502: closed (24.2.50; Debugger messes up current


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#12502: closed (24.2.50; Debugger messes up current-buffer)
Date: Wed, 03 Oct 2012 09:16:02 +0000

Your message dated Wed, 03 Oct 2012 11:14:55 +0200
with message-id <address@hidden>
and subject line Re: bug#12502: 24.2.50; Debugger messes up current-buffer
has caused the debbugs.gnu.org bug report #12502,
regarding 24.2.50; Debugger messes up current-buffer
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
12502: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12502
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.2.50; Debugger messes up current-buffer Date: Mon, 24 Sep 2012 10:31:04 +0200
The debugger now changes the current buffer in the following situation:

1. Create a file foo.el with this code:

(progn
  (require 'cl)
  (defun foo ()
    (with-current-buffer (get-buffer-create "test")
      (let ((b (current-buffer)))
        (debug)
        (assert (eq b (current-buffer)) t))))
  (foo))

2. In the foo.el buffer, evaluate the expression with C-x C-e

3. The debugger pops up with this message:
   Debugger entered: nil

4. Press c (i.e. debugger-continue)

5. The assertion fails with:
  Assertion failed: (eq b (current-buffer)), #<buffer test>, #<buffer foo.el>

This is a regression to older versions.


In GNU Emacs 24.2.50.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1)
 of 2012-09-22 on ix
Bzr revision: 110128 address@hidden
Windowing system distributor `The X.Org Foundation', version 11.0.10707000
Configured using:
 `configure '--with-jpeg=no' '--with-gif=no' '--with-tiff=no''




--- End Message ---
--- Begin Message --- Subject: Re: bug#12502: 24.2.50; Debugger messes up current-buffer Date: Wed, 03 Oct 2012 11:14:55 +0200
>> Thanks for the report.  Would the attached patch fix it?
>
> Yes, that seems to fix the problem.

Installed.  Bug closed.

> But the save-exursion in line 218
> looks now supsisously irrelevant.

I left it in because IIUC it can't do any harm.

martin


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]