Debugger - Breakpoint issue

KentR · Joined: 21 Jun 2010 Posts: 11

I am using the ICD-U64 programmer/debugger, along with the newest PCWH compiler (v4.121) targeting a PIC18F26J13.

My problem is that when I use the Debugger feature, there are certain C modules that I can set breakpoints, but there are other C modules where it does not allow me to set a breakpoint. I get the following error message:

"Error adding the breakpoint at c:\myfile.c, line 206. Could not resolve line number information. Make sure it belongs to the debugging session"

I have seven *.c modules in my project, and it will only allow me to add breakpoints in three of them.

Has anyone else seen this and found a solution to it?

Thanks!

andre schoeman · Joined: 20 Aug 2011 Posts: 2

Hi

I'm using ICD-U64 and PCWHD V4.124. I have the same problem.
I can't add breakpoints in any .c file other than the primary file created by the project.

I have tried re-installing the software without success.

Have you had any luck on this issue?
Thanks
Andre

Coffee · Joined: 10 Feb 2015 Posts: 9

I came across your questions... you probably have already resolved your problem. However, I did not see a resolution posted on the forums.

Check to see if you have the directive #nolist in your *.c files OR in any *.h files that are included by them. That apparently removes information the debugger needs to match code and line numbers. So, breakpoints can not be set as needed.

andre schoeman · Joined: 20 Aug 2011 Posts: 2

Hi

Sorry, I never got to the bottom of this one. I stopped using the compiler because the project was cancelled. I have not used it since.

Good luck,
Andre

allenhuffman · Posted: Wed Jun 19, 2019 8:21 am

This just started happening to me today. Everything was running and debugging fine, then suddenly...
_________________
Allen C. Huffman, Sub-Etha Software (est. 1990) http://www.subethasoftware.com
Embedded C, Arduino, MSP430, ESP8266/32, BASIC Stamp and PIC24 programmer.
http://www.whywouldyouwanttodothat.com ?

Ttelmah · Joined: 11 Mar 2010 Posts: 19546

You are using Custom Computer Services CCS C, not Ti CCS C?
The former only seemed to do this with a few very old versions
(when this thread was launched), the latter has several versions that
give this problem.
This forum is for the former C, not the latter.

allenhuffman · Posted: Wed Jun 19, 2019 12:19 pm

Ttelmah · Joined: 11 Mar 2010 Posts: 19546

The information used by the debugger is the .sym file, and the .cof file.
#nolist turns off generation of sym list data (and is by default set for the
CCS 'core' code - you can enable it by remming this out in the start of
the processor.h file). Since this contains the listing for everything, it
sounds as if the issue is in the .cof file. This can be disabled in the project
settings, but again this would affect all files.
Also most debuggers are limited in how many breaks they can generate.
If you have an issue again try right clicking on the break window and
disabling all breaks. You may find it starts working again.