search

Autodesk-AutoCAD / AutoLispExt

Visual Studio Code Extension for AutoCAD® AutoLISP
https://marketplace.visualstudio.com/items?itemName=Autodesk.autolispext
Apache License 2.0
83 stars 30 forks source link

Errors after Break set in VS Code #182

Open MarkMitchellADP-Resources opened 2 years ago

MarkMitchellADP-Resources commented 2 years ago

Describe the bug Issue Type: Bug

AutoCAD AutoLISP Extension running in Visual Studio Code Every time I set a break point: On running the code I get, "error: malformed list on input" This has nothing to do with the soundness of the code. It is a perfectly formed list.

A/B Experiments

To Reproduce Steps to reproduce the behavior:

  1. ACAD 2023 -
  2. Lispsys 1
  3. _vlide
  4. open a lisp file (one that is a good example of code.)
  5. set a break point
  6. F5 to start debug and download the lsp to your dwg
  7. run the lsp command.
  8. Produces error: "error: malformed list on input"

Expected behavior When execution reaches the break point the lsp halts so the variables can be examined.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information): VS Code version: Code 1.67.0 (https://github.com/microsoft/vscode/commit/57fd6d0195bb9b9d1b49f6da5db789060795de47, 2022-05-04T12:06:02.889Z) OS version: Windows_NT x64 10.0.18363 Restricted Mode: No

System Info Extensions (21) Additional context Add any other context about the problem here.

nigma456 commented 2 years ago

We don't his this problem for a good lisp file. Do you have tried to set Lispsys= 0 and the legacy IDE?

MarkMitchellADP-Resources commented 2 years ago

Nigma, Yes, in the legacy I don’t have the same problem. It just started doing this about a month ago. Just after a VSCode update. I started by posting the error to VSCode. They said it was probably the extension. If you can’t reproduce the error, I’m back to VScode (which is a better editor than the classic), but if I can’t find the cause, I’ll have to debug using the classic (Afterall, I used the classic for years.). Can you think of any settings that I may have changed intravitally that would cause this problem. Mark

From: nigma456 @.> Sent: Friday, May 6, 2022 7:12 PM To: Autodesk-AutoCAD/AutoLispExt @.> Cc: Mark Mitchell @.>; Author @.> Subject: Re: [Autodesk-AutoCAD/AutoLispExt] Errors after Break set in VS Code (Issue #182)

We don't his this problem for a good lisp file. Do you have tried to set Lispsys= 0 and the legacy IDE?

— Reply to this email directly, view it on GitHubhttps://github.com/Autodesk-AutoCAD/AutoLispExt/issues/182#issuecomment-1120111389, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUNLMNN37ZBY2IMIPJHQDFTVIXGN7ANCNFSM5VJPNQ5Q. You are receiving this because you authored the thread.Message ID: @.**@.>>

JDSComm commented 2 years ago

I had a similar, but a bit different issue occur.

5-6-2022 Using VSCode, this suddenly started happening in the middle of debugging code. VSCode was working fine with breakpoints in the code. Then, all of a sudden, when the code was stopped on a breakpoint my variables were all nil. Looking at the Debug Console I noticed this error "warning: unwind skipped on exception". After digging into this I have discovered that this is only occurring if I have breakpoints in the code. If I remove ALL the breakpoints the code will run fine in the VSCode debugger. I shut down my PC and then tried again but the same thing still happens. I tried debugging the same file, with the same breakpoint, in the VLisp editor and it worked fine, no error, variables had values.

I thought I found a solution: I uninstalled the AutoCAD AutoLISP Extension and then re-installed it. I can now debug with breakpoints in VSCode again.

But the problem occurred 2 more times within a week of each other. The first of those 2 times I was able to fix it with the extension uninstall and reinstall method but the last time it happened this no longer works.

So in order to get anything done i have gone back to VLIDE which is too bad because I like VSCODE better in many respects but it does not seem to be a stable extension yet.

Autodesk, Please fix the extension!

Based on the fact that your issues started the same day as mine I tried uninstalling ver. 1.5.0 of the extension and installing 1.4.0. It still does not work, kind of expected it since 1.5.0 has been out for more than a year.

Autodesk, Please fix the extension!

MarkMitchellADP-Resources commented 2 years ago

JDSComm, I was told by the Autodesk team assigned to VSCode that unless they can reproduce the problem, they can’t fix it. (Yes, I understand.)

It is allusive. I continued to use the broken VSCode for writing code. And trying to use the debugger once each time, before switching to the other ACAD editor. I got the error message popup “error: malformed list on input". I ignored it and ran the next line of code. {Then STOP executing. Or finished execution normally. This is a bit fussy.} Anyhow, now my VSCode is fixed. Breakpoints work. Variables are full. Everything is wonderful…….. Until it is not.

JDSComm please don’t give up using the VSCode. At least try once each time you start a debug session. And post. What you find. (Even if it is redundant.) After I got the fix. I just plugged on coding; I didn’t leave the above “fix”. Sorry, I thought I was the only one with this anomolly. The error "warning: unwind skipped on exception" is a good clue. I will watch for it, next time it breaks. It does seem to break when I jump out prematurely. (Not sure, because whatever I do that cause it, I don’t usually recognize it until the break point doesn’t work.) I don’t want to go out of my way to break it, because I don’t know if I can fix it again.

But soon or later, it will break. I will post anything that I can find about how it broke. Please do the same. We will win this.

Thank you so much for your response (Hurray, I’m not crazy. There is someone else. …. ??? …. Sorry for your loss,) Mark

From: JDSComm @.> Sent: Thursday, June 9, 2022 8:42 AM To: Autodesk-AutoCAD/AutoLispExt @.> Cc: Mark Mitchell @.>; Author @.> Subject: Re: [Autodesk-AutoCAD/AutoLispExt] Errors after Break set in VS Code (Issue #182)

I had a similar, but a bit different issue occur.

5-6-2022 Using VSCode, this suddenly started happening in the middle of debugging code. VSCode was working fine with breakpoints in the code. Then, all of a sudden, when the code was stopped on a breakpoint my variables were all nil. Looking at the Debug Console I noticed this error "warning: unwind skipped on exception". After digging into this I have discovered that this is only occurring if I have breakpoints in the code. If I remove ALL the breakpoints the code will run fine in the VSCode debugger. I shut down my PC and then tried again but the same thing still happens. I tried debugging the same file, with the same breakpoint, in the VLisp editor and it worked fine, no error, variables had values.

I thought I found a solution: I uninstalled the AutoCAD AutoLISP Extension and then re-installed it. I can now debug with breakpoints in VSCode again.

But the problem occurred 2 more times within a week of each other. The first of those 2 times I was able to fix it with the extension uninstall and reinstall method but the last time it happened this no longer works.

So in order to get anything done i have gone back to VLIDE which is too bad because I like VSCODE better in many respects but it does not seem to be a stable extension yet.

Autodesk, Please fix the extension!

— Reply to this email directly, view it on GitHubhttps://github.com/Autodesk-AutoCAD/AutoLispExt/issues/182#issuecomment-1151296421, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUNLMNMXO4FKUMRNLR6JWGTVOIGC5ANCNFSM5VJPNQ5Q. You are receiving this because you authored the thread.Message ID: @.**@.>>

JDSComm commented 2 years ago

I have it working again, I think, for now.... I ended up reverting back to a previous version of VSCode ver. 1.66.2 (User setup). Make sure to turn off automatic updates in VSCode. Back to using ver. 1.5.0 of the Autodesk AutoLISP Extension.

We will see....

MarkMitchellADP-Resources commented 2 years ago

I noticed an error had happened while testing some code. The code abended. I hit esc a couple of times to reset and got “Exception has occurred. bad argument value: AcDbCurve 43, now when setting a break point and rerunning the code at the breakpoint I get the error message popup “error: malformed list on input".

error message popup “ST2 did not end normally." (My error exit routine.) In the console the breakpoint code is still highlighted. I press (To continue execution.) Code continues to run in acad window to completion. Run code again. Breakpoints work. Variables are full. Everything is wonderful. code completes in acad window.
JDSComm commented 2 years ago

So, reinstalling an old version of VS Code only fixed the problem for 8 days. So, now I have done a partial clean uninstall of VS Code by just deleting 2 folders as described here https://code.visualstudio.com/docs/setup/uninstall under "Clean uninstall".

After restarting VS Code and reloading the extension and making my customizations this seems to have worked. At least now I'm fairly certain that file or files in one or both of those folders is causing this issue.

If this works for you, make and keep a copy of those two folders somewhere to make reconfiguring easier next time if needed.

Currently running VS Code version 1.68.1 (user setup) with ver. 1.5.0 of the Autodesk AutoLISP Extension.

MarkMitchellADP-Resources commented 2 years ago

Thank you for the update. I am on production drafting for a couple more weeks. Then I will try your fix, before starting coding efforts. Mark

From: JDSComm @.> Sent: Monday, June 20, 2022 10:09 AM To: Autodesk-AutoCAD/AutoLispExt @.> Cc: Mark Mitchell @.>; Author @.> Subject: Re: [Autodesk-AutoCAD/AutoLispExt] Errors after Break set in VS Code (Issue #182)

So, reinstalling an old version of VS Code only fixed the problem for 8 days. So, now I have done a partial clean uninstall of VS Code by just deleting 2 folders as described here https://code.visualstudio.com/docs/setup/uninstall under "Clean uninstall".

After restarting VS Code and reloading the extension and making my customizations this seems to have worked. At least now I'm fairly certain that file or files in one or both of those folders is causing this issue.

If this works for you, make and keep a copy of those two folders somewhere to make reconfiguring easier next time if needed.

Currently running VS Code version 1.68.1 (user setup) with ver. 1.5.0 of the Autodesk AutoLISP Extension.

— Reply to this email directly, view it on GitHubhttps://github.com/Autodesk-AutoCAD/AutoLispExt/issues/182#issuecomment-1160676242, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUNLMNIVBOYVA44SHXCIPODVQCQSJANCNFSM5VJPNQ5Q. You are receiving this because you authored the thread.Message ID: @.**@.>>

JDSComm commented 1 year ago

See the attached file. First to get VSCode working again perform the steps in "SOLUTION 2". Then, If this ever happens again, all you have to do is "SOLUTION 3" or "SOLUTION 3 Update".

I was about to give up on VSCode because of this but now I'm not having any issues with it.

VSCode - Unwind skipped on exception error if breakpoint in code.txt