6 hours for a comma, a space, and some caps.....

[Darrel Taylor]

I meant it for troubleshooting only Darrel, not to steal your code. Of course the final cut must use it as "licensed" by you, as an include file.

Well, the only "License" is ... Yours to use as you see fit.

So it's just my own personal problem, wish, desire ... peeve.

I seem to be getting more of those, which are Directly proportional to the lack of color in my hair at any given time.
<br>

[Archangel]

Well, the only "License" is ... Yours to use as you see fit.

So it's just my own personal problem, wish, desire ... peeve.

I seem to be getting more of those, which are Directly proportional to the lack of color in my hair at any given time.
<br>

Well Darrel, most of here are Gentlemen / persons. Your generosity has provided us all with talent, most of us do not have, and we are grateful. So the " license " is not to tick you off. Now as for hair color . . . at least you have some ! I encourage everyone to use the code you provided as you prescribed as includes. Copy past should be reserved for troubleshooting only, and the final cut should / must be as includes.

[boroko]

I have thought about it, and listing all of the code in sequence would not have pointed out my problem in this situation. It may have given me some idea of line number, but it would not have helped.

With that in mind, are there any better ways to help see these obscure problems?
The whole point of this thread was to help identify troubleshooting techniques.
In this case, the only thing that helped me was stubbornness and stripping things down until there was nothing left that could be wrong. Then I started adding back sections until the problem reoccurred. Case sensitive searches of the same variables pointed out the caps problem. Nothing brilliant, but things that I hadn't thought to do right away. Oh, that.... and a bunch of luck.

Bo

[Darrel Taylor]

With that in mind, are there any better ways to help see these obscure problems?

With the code from post#1, the first error you would have received would be ...
Found label after column 1. (INT_HANDLER).

That narrows it down to one of 3 lines in the program.
Technically, it points to the exact line, since it was the only one with INT_HANDLER in upper case.
Commenting the lines would have easily shown which one was the problem.

Often, it's not the line numbers in the error that give the best indications, but the (words in brackets) at the right end of the error.
And start from the top of the error list. The first one listed is usually the most important, and resolving that one frequently fixes many of the following errors too.
<br>

[boroko]

As a matter of fact,

Found label after column 1. (INT_HANDLER).

was exactly what I saw first. The problem for me was that it referenced something like line 1400 and I had not noticed the caps problem. The line number tempted me to start looking in your program to see if I could get any hints of something that I hadn't done right. I hadn't for a minute thought that your program was at fault. I was more concerned that I hadn't passed a correct parameter. I saw that DT_INTS had special handling for the 18F1230 on it's comparator interrupt and started to wonder if it was a situation similar to the 8 pin devices where GPIO aliased to some other name. A few hours were spent in that loop until, in desperation I just stripped the bone and started to make some progress.

It was kind like "where's Waldo" for a while looking between the 2 copies until it started to become clearer.

Again, I'm trying to pry some tricks out of the group to elevate the process for the less experienced. I'm still one of them, but I'm becoming "less" less experienced.

Bo