command line troublesooting

[Anonymous]

I am used to being able to type !C:MYFUNC at the ACAD command prompt to get
the list of what defines C:MYFUNC and also, I am used to seeing the line of
the LISP that failed along with the code that was running when a LISP has an
error. How can I get this info conveniently in ACAD 2002 so that I can
trouble shoot my routines?

Thanks,
Eric

[Anonymous]

Use the VLIDE. Much more powerful than a simple screen dump.

--
R. Robert Bell, MCSE
http://www.acadx.com


"Eric Eden" wrote in message
news:7E937E39DB3C50A3CD676A47DB89A746@in.WebX.maYIadrTaRb...
| I am used to being able to type !C:MYFUNC at the ACAD command prompt to
get
| the list of what defines C:MYFUNC and also, I am used to seeing the line
of
| the LISP that failed along with the code that was running when a LISP has
an
| error. How can I get this info conveniently in ACAD 2002 so that I can
| trouble shoot my routines?
|
| Thanks,
| Eric
|
|

[Anonymous]

While troubleshooting, use defun-q instead of defun.

--
John Uhden, Cadlantic/formerly CADvantage
--> mailto:juhden@cadlantic.com
--> http://www.cadlantic.com
2 Village Road
Sea Girt, NJ 08750
Tel. 732-974-1711
FAX 732-528-1332

"Eric Eden" wrote in message
news:7E937E39DB3C50A3CD676A47DB89A746@in.WebX.maYIadrTaRb...
> I am used to being able to type !C:MYFUNC at the ACAD command prompt to
get
> the list of what defines C:MYFUNC and also, I am used to seeing the line
of
> the LISP that failed along with the code that was running when a LISP has
an
> error. How can I get this info conveniently in ACAD 2002 so that I can
> trouble shoot my routines?
>
> Thanks,
> Eric
>
>

[Anonymous]

ok....
I cannot do my job all of a sudden; I have a routine that works on a file on
my C: drive but not on a network drive, and I cannot get ACAD to tell me
where the LISP is failing! I have always coded my LISP in a text editor
and debugged in ACAD.....

I am trying to use the VLIDE... I have tried to find out how to run a lisp
and have the VLIDE show me the error, but I have not yet figured it out....
I can't even figure out how to run the routine... but I will....

I will read the VLIDE manual, but if someone can give me some quick hints to
get me going, I would appriciate that.

Thanks for the defun-q hint. That lets me use !C:MYFUNC to list the
function, but it still does not tell me where my routine failed....

Thanks in advance,
Eric Eden


"Eric Eden" wrote in message
news:7E937E39DB3C50A3CD676A47DB89A746@in.WebX.maYIadrTaRb...
> I am used to being able to type !C:MYFUNC at the ACAD command prompt to
get
> the list of what defines C:MYFUNC and also, I am used to seeing the line
of
> the LISP that failed along with the code that was running when a LISP has
an
> error. How can I get this info conveniently in ACAD 2002 so that I can
> trouble shoot my routines?
>
> Thanks,
> Eric
>
>

[Anonymous]

In the vlide, go to the Debug menu and check Break On Error. Then run your
routine. When it breaks, go back to the Debug menu and select last break
source. This will highlight the line of code that's breaking. Do some
quick reading on adding watches to watch your variables values and on
setting break points & stepping thru your code line by line. Good Luck.
--
Bobby C. Jones
Dots & Parens living in harmony...

[Anonymous]

Thanks, Bobby....

Eric


"Bobby Jones" wrote in message
news:A9DF94CD21856D90A93756CC84D1EC8D@in.WebX.maYIadrTaRb...
> In the vlide, go to the Debug menu and check Break On Error. Then run
your
> routine. When it breaks, go back to the Debug menu and select last break
> source. This will highlight the line of code that's breaking. Do some
> quick reading on adding watches to watch your variables values and on
> setting break points & stepping thru your code line by line. Good Luck.
> --
> Bobby C. Jones
> Dots & Parens living in harmony...
>
>
>