VLIPS not highlighting error break point

[126843]

Why my VLISP is not highlighiting text?

I wanted to learn how to debug using VLISP so i stardet with this tutorial

http://www.lee-mac.com/debugvlide.html

I followed presented steps, but my VLISP insted of highlighting error place is displaying me a message in new window.

Is there any option in VLISP to change this?

Here you can se attached picture. 

[martti.halminen]

I'm not sure about your exact workflow, but some notes on debugging with VLIDE:

- Only works for interpreted code (loaded as .lsp), stuff loaded as .fas or .vlx isn't accessible

- Merely opening a .lsp file in VLIDE is not enough, you also need to load it into the Lisp environment, either by a (load ...) function call or by the Load active edit window -icon in the toolbar.

- Break on Error just throws you to the debugger on error. To see the error location you also need to use the Debug>Last Break Source -menu command or the corresponding icon.

-- 

[Anonymous]

Thnsks for reply Martti

This is my second account ( i hope this is not a problem).

About my workflow: I am not sure about you talking about but my worflow look like this: I open VLISP trough ACAD write some function and save as .lsp

My VLISP is in polish languegae but this alert window which i posted in picture in previous post shows up when i hit CTRL + F9 ( which propabbly corresponds to your Debug-> Last break source)

How you suggest to debug lisp? Or maybe you have link to better tutorial  about using VLISP ( can be in ENG its not a problem)

[Anonymous]

CNTL-F9 is the correct way, usually, to deal with an unplanned break/error.

 Some errors won't highlight the offending text....for some reason.

Your error is for "zly" being nil and then trying to do an entity process on it (like entget, or assoc, etc....).

You can use the "load selection" button/command (cntrl+shift+E, or button on toolbar) to run your code a line at a time and try and find out where you went nil.

[martti.halminen]

---

@Anonymous wrote:

Thnsks for reply Martti

This is my second account ( i hope this is not a problem).

About my workflow: I am not sure about you talking about but my worflow look like this: I open VLISP trough ACAD write some function and save as .lsp

My VLISP is in polish languegae but this alert window which i posted in picture in previous post shows up when i hit CTRL + F9 ( which propabbly corresponds to your Debug-> Last break source)

How you suggest to debug lisp? Or maybe you have link to better tutorial  about using VLISP ( can be in ENG its not a problem)

---

I get this behaviour only when the error is in compiled code (loaded as .fsl or .vlx). When the error is in a .lsp which has been loaded into the lisp environment (not just opened as a file in VLIDE), CTRL-F9 writes the error report in the Lisp Console window and jumps to the source.

Try View>Trace Stack  (or Ctrl-Shift-T) to see what your program was doing when it broke.

Or the last resort, put a breakpoint somewhere before the error, and step (F8) until you hit the error.

--