Is dis470.exe '--all' option in 4.6.1 toolset compatible with EABI? I am getting this error:
"dis470.exe" --all --ual --hex --runtime_addr --raw_registers "m3.out">> error: record 0 in table .cinit has load address 0x168; no section found at that address
Eugene
Yes, it is intended to be compatible, and it works in the examples I tried. I recommend you submit the test case so it can be analyzed.
Did you test it for -mv7M3 and locating code and .cinit with different load/run addresses? I can give you test case.
We did more tests with 4.6.2 tool set and the problem is still there. Test case will be:
- Link code with --abi=eabi, -mv7M3, -mt, --absolute_exe, --rom_model
- Set different load and run address for initialized sections
- have some global RAM initialized variables make .cinit to appear in the image
- run dis470.exe --all --ual --hex --runtime_addr --raw_registers ...
The mentioned error will be there. If global initialization is removed and image does not have .cinit section then --all option will work.
I'm sorry, I'm still having trouble reproducing this problem. Could you please submit a complete test case, including the source code, compilation options for each step, and the linker command file?
I can reproduce this problem. I suspect it is a bug in the disassembler. I filed SDSCM00034933 in our ClearQuest system. You are welcome to track progress on this issue here https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDo-Web&contextid=SDOWP&rmsessionid=4456b2be-110d-4d53-ba14-c0a8f08f4205 . Enter the CQ number in the "Find Record ID:" box.
Thanks and regards,
-George
TI C/C++ Compiler Forum ModeratorPlease click Verify Answer on the best reply to your question.The Compiler Wiki answers most common questions.Track an issue with SDOWP. Enter your bug id in the "Find Record ID" box.