Include Files Breaking Debugger

dthorson

Can no longer DEBUG?.after using .axi files

I?m using 2 include files in a program for plasma control. But doing so seems to prevent me from stepping through code and debugging.

I?ve tried to include the files in different locations DEFINE_DEVICE, DEFINE_START with no luck.

Is there a work around for this, or is it something in my code?

vining

I find debug w/ break points hit or miss. Some times they work great inside modules and includes and some times I can't get them to work in the main.axs. I remember in Pro-II the instructor had a hard time with it so I don't know what the secret is. I can go an entire day w/o getting a break point to work and the next day it's fine.

If any of you smart programmers types know the secret or have any tips or trick feel free to share!

mpullin

suggestion for debugging w/ includes

1) Replace each #include some_file.axi; line with the entire contents of that axi.
2) Debug.
3) Make changes.
4) Repeat steps 2-3 as often as desired.
5) Put the #includes back in. Test once more for posterity.

dthorson

Well that did the trick. Thanks for the work around, it's exactly what I was looking for.

It's not a permanent fix but I can get by with it.

Thanks!

ericmedley

vining wrote:

I find debug w/ break points hit or miss. Some times they work great inside modules and includes and some times I can't get them to work in the main.axs. I remember in Pro-II the instructor had a hard time with it so I don't know what the secret is. I can go an entire day w/o getting a break point to work and the next day it's fine.

If any of you smart programmers types know the secret or have any tips or trick feel free to share!

I've had the same experience. I've just kinda came up with different ways to debug a program, myself. I'll load values into dummy variables to watch the process or send a bunch of messages to the master via port 0. After I've determined what's going on, I'll delete out all the diagnostic stuff, recompile and call it good.