Hello Ionana!
Checking in the CodeWarrior Debugger Manual, I found the following:
Correct module names are displayed in the Module component window.
Make sure that the module name of a command that you implement is
correct:
If the .abs is in HIWARE format, some debug information is in the
object file (.o), and module names have a .o extension (e.g., fibo.o).
In ELF format, module name extensions are .c, .cpp or .dbg ( .dbg for
program sources in assembler) (e.g., fibo.c), since all debugging
information is contained in the .abs file and object files are not used.
So probably one of the modules or files its been corrupted or not properly imported, I would have to be more involved with your code to know.
Hope it helps.
Best regards!
Monica
Hello Ionana!
Checking in the CodeWarrior Debugger Manual, I found the following:
Correct module names are displayed in the Module component window.
Make sure that the module name of a command that you implement is
correct:
If the .abs is in HIWARE format, some debug information is in the
object file (.o), and module names have a .o extension (e.g., fibo.o).
In ELF format, module name extensions are .c, .cpp or .dbg ( .dbg for
program sources in assembler) (e.g., fibo.c), since all debugging
information is contained in the .abs file and object files are not used.
So probably one of the modules or files its been corrupted or not properly imported, I would have to be more involved with your code to know.
Hope it helps.
Best regards!
Monica
You were right. I removed the library d4d_libs08.lib and the error disappeared. But I don't know why the error appeared in the first place considering that I have another library d4d_libscf.lib that doesn't causes any problems. Anyway, thank you for the answer. :smileygrin: