Hi,
I start to use Linary AArch64 toolchain recently and just joined this maillist. I went through some of the archived threads but didn't read all of them. So bear me if I'm asking dumb question or old question which had been answered before.
For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or AArch32 state. My questions are:
1) Is the aarch64-none-elf-gdb.exe good for both AArch64 and AArch32 or I have to run the arm-none-eabi-gdb.exe if the target running in AArch32 state?
2) If the target is in AArch64 state, can I use the aarch64-none-elf-gdb.exe to load binary built for AArch32 to the target?
I'm really appreciated if anybody can help me on these two questions.
Thanks in advance,
StrongQ
On 17 October 2014 16:28, Qu, Strong strongq@qti.qualcomm.com wrote:
For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or AArch32 state. My questions are:
Is the aarch64-none-elf-gdb.exe good for both AArch64 and AArch32 orI have to run the arm-none-eabi-gdb.exe if the target running in AArch32 state?
I think last time I asked this (which was some time ago) the answer was that you have to use the gdb for the relevant target. You can build support for both targets into one gdb binary (and then select with "set arch arm" or "set arch aarch64") but I think that any particular debug session must be one or the other. I'm told that x86 also has this restriction, which makes it tricky to debug across the early boot switch it does from legacy 8086 code to 64 bit.
Hopefully one of the gdb developers will know if the situation has changed.
thanks -- PMM
On 21 October 2014 12:51, Peter Maydell peter.maydell@linaro.org wrote:
On 17 October 2014 16:28, Qu, Strong strongq@qti.qualcomm.com wrote:
For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or AArch32 state. My questions are:
Is the aarch64-none-elf-gdb.exe good for both AArch64 and AArch32 orI have to run the arm-none-eabi-gdb.exe if the target running in AArch32 state?
I think last time I asked this (which was some time ago) the answer was that you have to use the gdb for the relevant target. You can build support for both targets into one gdb binary (and then select with "set arch arm" or "set arch aarch64") but I think that any particular debug session must be one or the other. I'm told that x86 also has this restriction, which makes it tricky to debug across the early boot switch it does from legacy 8086 code to 64 bit.
Hopefully one of the gdb developers will know if the situation has changed.
thanks -- PMM
linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
As of now for AArch32 binaries aarch64-*-gdb will be used and arm-*-gdb will be used to debug AArch32 binaries.
GDB still only allows a debug session to be of any of the one architectures and not both.
-- Omair
linaro-toolchain@lists.linaro.org
-
Omair Javaid -
Peter Maydell -
Qu, Strong