[Top][All Lists]

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

Entering backtrace buffer if displayed information is huge

From: Wolfgang Pausch
Subject: Entering backtrace buffer if displayed information is huge
Date: Mon, 7 Oct 2019 17:29:54 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0


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

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

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

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

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

Thanks for all hints,


reply via email to

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