[Top][All Lists]

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

Re: Entering backtrace buffer if displayed information is huge

From: Robert Pluim
Subject: Re: Entering backtrace buffer if displayed information is huge
Date: Tue, 08 Oct 2019 14:13:18 +0200

>>>>> On Mon, 7 Oct 2019 17:29:54 +0300, Wolfgang Pausch <address@hidden> said:

    Wolfgang> Hello,
    Wolfgang> I'm implementing some lisp code based on js2-mode.  The nodes of 
    Wolfgang> abstract syntax tree of that mode frequently need to be passed 
    Wolfgang> defuns.

    Wolfgang> My problem is that the Backtrace buffer tries to display the huge
    Wolfgang> contents of that nodes, and this makes entering the Backtrace 
    Wolfgang> extremely slow, and sometimes impossible at all.

    Wolfgang> (and once opened, each editor move within the Backtrace buffer can
    Wolfgang> cause emacs to freeze for an additional time)

    Wolfgang> What's a senseful way to debug in such situations?  Basically, if 
    Wolfgang> contents of the variables passed to a defun are too huge to be
    Wolfgang> displayed in a efficient manner, at least the names of the 
    Wolfgang> being called would be a help while debugging --- is it somehow
    Wolfgang> possible to restrict opening a Backtrace buffer to such more basic
    Wolfgang> information?

    Wolfgang> Currently, I have the situation that debugging trivial programming
    Wolfgang> problems costs way too much time...

    Wolfgang> Thanks for all hints,

Does setting 'print-length' to something sensible help?


reply via email to

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