日本語
Using SH-4a GDB with renesas built image
Using SH-4a GDB with renesas built image
Is it possible to use Sh-gdb to debug a binary that is built using Renesas toolchain?
Thanks,
John
Hello John,
Thank you for reaching out to us!
Yes, it is possible to use SH-GDB to debug a binary built with the Renesas SHC Toolchain, however there are some incompatibilities between the two: the process, for example, is handled by sh_converter.exe in e2Studio. We therefore recommend you use SH-GDB under e2Studio directly, for best compatibility.
—
Thank you,
Adrian
The GNU Tools Support Team
-
John -
Hello Adrian,
Thanks a lot for the fast response.
As much as I know that e2Studio isn’t supporting sh-4a, so I think it wouldn’t work for me.
The problem I face when using SH-GDB, is that when using the “step” or “next” commands, it gives me the “cannot find bounds of current function” error.
Also, it doesn’t stop at breakpoints.
Could it be something related to the Renesas – GNU compatibility, since I am building using Renesas toolchain and debugging using SH-GDB.Thanks,
John -
Hello John,
Thank you for your feedback!
We appreciate the thorough description of the issue you have encountered – it is helpful in tracing down the root of the problem.
Therefore, we just wanted to let you know that we are now working on reproducing the issue and we will let you know our conclusion as soon as possible.—
Thank you,
Adrian
The GNU Tools Support Team -
Hello John,
Thank for your patience, much appreciated!
While we are still investigating your raised issue, we wanted to let you know that because you’re not using e2 studio, you need to get the latest sh-elf-gdb.exe and sh-converter.exe out of e2 studio, in order to use them as follows:
1. build your project with the Renesas SHC toolchain;
2. convert the output elf file with sh_converter.exe;
3. debug the converted elf file using sh-elf-gdb;You will find sh-elf-gdb.exe and sh-converter.exe in \DebugComp. If you haven’t used e2 Studio for SH before, the files will not be there – so you will need to create a dummy (SH 2) e2 Studio project and try to debug it, in order for the files to be extracted.
—
Thank you,
Adrian
The GNU Tools Support Team -
John -
Thanks for the help and detailed steps, it helped me a lot.
It works when using the converter you mentioned, I’d like to add that the converter’s name I found in e2studio is “renesas_cc_converter.exe”.
Also, could you please let me know when the KPIT sh-elf-gdb is fixed so that it can be used to debug a binary built using Renesas toolchain.
Best Regards,
John Emad -
Hello John,
The problem is that the SHC toolchain does not fully comply with the DWARF standard – this is why a conversion step is needed to help remove those incompatibles. Unfortunately, sh-elf-gdb will not be fixed as a result thereof. We hope this helps.
—
Kind regards,
The GNU Tools Support Team
Hi John,
Based on my understanding, ‘renesas_cc_converter.exe’ is being used for CCRL (Renesas RL78). Support team should be able to confirm this.
And Renesas RXC/CCRX toolchain uses DebugComp\RX\rx_converter.exe. i.e., rx converter is used to convert the Renesas RXC / CCRX output file format into GNU debugging format.
For SH, you should use the sh_converter.exe
Hi John,
The sh converter should be located in the DebugComp\SH\ directory e.g., e2studio_4.x.x.xx\DebugComp\SH\sh_converter.exe
This is shipped as part of “SH” e2 studio components i.e., SH is provided as an installable package as part of e2 studio installer, please ensure you have selected the SH components during e2 studio installation.
Please also have the SHC/GNUSH toolchains installed and integrated with e2 studio.
Create a dummy project and attempt debugging. This should extract the relevant components in the DebugComp\SH\ directory.
Or you may request the GNU Team to provide the sh_converter.exe
-
John -
Yeah, I found it.
Adrian, said it is in \DebugComp, so I thought you were talking about “renesas_cc_converter.exe”.
So, both exists … “renesas_cc_converter.exe” in “\DebugComp” and “sh_converter.exe” in “\DebugComp\SH”.
Also the describtion of both is the same except for the version number:
———————–
DWARF converter tool v2.2.0
This tool modifies DWARF debug information generated by Renesas proprietary
toolchains to enable debugging with the GNU debugger (GDB).For more information contact gnusupport@kpitgnutools.com.
Usage sh_converter.exe
———————–
DWARF converter tool v2.4.10
This tool modifies DWARF debug information generated by Renesas proprietary
toolchains to enable debugging with the GNU debugger (GDB).For more information contact gnusupport@kpitgnutools.com.
Usage renesas_cc_converter.exe [-dsp_section=,,…]
———————–Do you know if there is a difference between them or not?
-
Hello John,
About the difference between the sh_converter.exe and renesas_cc_converter.exe, we want to let you know that they are practically built from the same sources, but the differences are:
– sh_converter.exe has been developed/tested with the SHC toolchain, while the renesas_cc_coverter has been developed/tested for the CCRL toolchain (for RL78);
– the reason for which it worked with renesas_cc_converter.exe is because the CCRL toolchain has similar incompatibilities with DWARF as the SHC toolchain has, but the only downside of sh_converter.exe is that it hasn’t been updated from quite some time, so it doesn’t contain the latest fixes;
– sh_converter.exe is the only one dedicated from SHC.—
Thank you,
Adrian
The GNU Tools Support Team
How about converting the Renesas output file into a GNU compatible format on command line by using the sh_converter.exe (available along with e2 studio) and then debugging using SH GDB?
-
John -
This one works, thanks a lot for the help.
I’d like to add that the converter’s name I found in e2studio is “renesas_cc_converter.exe”.
