-
-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bencode parsing issues #597
Comments
We need to implement some explicit check for incomplete messages. The current code assumed that all decode errors were the result of incomplete messages, but that's not always the case. |
In both cases above, the result was that no stacktrace was shown, so processing the messages didn't complete. |
The unblanced parenthesis message is actually coming from |
And I believe the reason that |
I noticed something similar yesterday. Code evaluated with |
That's a good idea anyway, as a compilation error isn't always caused by code in the buffer being loaded. |
I am noticing the itneger-or-marker error when I evaluate (+ aa bb) in a new project. The backtrace is
|
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#583 and clojure-emacs#586.
Probably also fixes the related clojure-emacs#586.
[Fix #597] Don't process incomplete messages unless sure
Probably also fixes the related clojure-emacs#586.
I'm seeing some bencode parsing issues. This occurs when processing a stacktrace message following an exception thrown via
load-file
(though I don't think that is relevant).This sometimes appears as:
and sometimes as:
In each case the problem seems to be related to emacs trying to process a bencoded message that has a length of 4096 bytes and is incomplete. The first error above seems to occur when the trucation occurs within a bencode header, the second when the trunction occurs in the message data.
The text was updated successfully, but these errors were encountered: