[Top][All Lists]

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

[debbugs-tracker] bug#24514: closed (24.5; [WIP][PATCH] Lispy backtraces

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24514: closed (24.5; [WIP][PATCH] Lispy backtraces)
Date: Wed, 12 Oct 2016 15:36:02 +0000

Your message dated Wed, 12 Oct 2016 17:34:42 +0200
with message-id <address@hidden>
and subject line Re: 24.5; [WIP][PATCH] Lispy backtraces
has caused the debbugs.gnu.org bug report #24514,
regarding 24.5; [WIP][PATCH] Lispy backtraces
to be marked as done.

(If you believe you have received this mail in error, please contact

24514: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24514
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.5; [WIP][PATCH] Lispy backtraces Date: Fri, 23 Sep 2016 01:14:47 +0200 User-agent: Mutt/1.7.0 (2016-08-17)
I wrote a minimal patch that increases the overall consistency in a
backtrace buffer by printing the call stack frames as S-Expressions.


Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p t)
  +(1 t)
  eval((+ 1 t) nil)
  eval-expression((+ 1 t) nil)
  call-interactively(eval-expression nil nil)


Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p t)
  (debug error (wrong-type-argument number-or-marker-p t))
  (+ 1 t)
  (eval (+ 1 t) nil)
  (eval-expression (+ 1 t) nil)
  (funcall-interactively eval-expression (+ 1 t) nil)
  (call-interactively eval-expression nil nil)
  (command-execute eval-expression)

Now, this patch isn't perfect.  For some reason there's an extra debug
line in the second version, I've yet to investigate into the reason for
this.  The other problem is that while I can't imagine any reason to go
back to the original view of the backtrace, I cannot rule out that this
change might break other tools relying on it.  I'd appreciate any
feedback on this.

Attachment: 0001-Make-backtraces-great-again.patch
Description: Text Data

--- End Message ---
--- Begin Message --- Subject: Re: 24.5; [WIP][PATCH] Lispy backtraces Date: Wed, 12 Oct 2016 17:34:42 +0200 User-agent: Mutt/1.7.1 (2016-10-04)
Feature was fully implemented and committed to the respective branch.

--- End Message ---

reply via email to

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