Commit aabcee5d authored by David Byers's avatar David Byers
Browse files

Save backtrace and parser input on lyskom-protocol-error. Very experimental.

parent 76002bbe
1999-10-25 David Byers <davby@ida.liu.se>
* vars.el.in (lyskom-backtrace-list): New variable.
* parse.el (lyskom-char-p): Make lyskom-char-p ignore whitespace
to mimic behavior of lyskom-expect-char and friends.
(lyskom-protocol-error): Accumulate backtraces.
1999-10-20 David Byers <davby@ida.liu.se>
* mship-edit.el (lp--update-membership): When we set the priority
......
......@@ -99,7 +99,7 @@ first non-white character was not equal to CHAR."
(defun lyskom-char-p (char)
"Check if next token is CHAR (a character)."
(string-match (format "\\`%c[ \t\n\r]" char) (lyskom-string-to-parse)))
(string-match (format "\\`[ \t\n\r]*%c[ \t\n\r]" char) (lyskom-string-to-parse)))
(defun lyskom-string-to-parse ()
......@@ -1147,6 +1147,18 @@ functions and variables that are connected with the lyskom-buffer."
(format " Current string: ")
(buffer-substring lyskom-parse-pos (point-max))))
(lyskom-message "Saving debugging information...")
(setq lyskom-backtrace-list (cons (list (current-time-string)
(let* ((buffer (generate-new-buffer " *Backtrace*"))
(standard-output buffer))
(backtrace)
(prog1 (buffer-string buffer)
(kill-buffer buffer)))
(lyskom-string-to-parse))
lyskom-backtrace-list))
(lyskom-message "Saving debugging information...done")
(signal 'lyskom-protocol-error
(format "Protocol error in %S: %s"
function
......
......@@ -1715,6 +1715,9 @@ kom-go-to-next-conf might go to the same conference again.)")
(def-kom-var lyskom-debug-communications-to-buffer nil
"Non-nil means all communications with the server is stored in a buffer.
The name is stored in lyskom-debug-communications-to-buffer-buffer.")
(def-kom-var lyskom-backtrace-list nil
"List containing debugging information")
(def-kom-var lyskom-debug-what-i-am-doing t
"Non-nil means asynchronous message 5 will be logged to the debug
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment