Re: [PATCH] gdb-script: updated lx_current for riscv

From: Andrew Jones
Date: Sun Nov 13 2022 - 06:06:50 EST


On Fri, Nov 11, 2022 at 11:59:38AM -0800, debug@xxxxxxxxxxxx wrote:
> From: Deepak Gupta <debug@xxxxxxxxxxxx>
>
> lx_current python gdb command defined in scripts/gdb/cpus.py updated
> to support riscv architecture.
>
> Signed-off-by: Deepak Gupta <debug@xxxxxxxxxxxx>
> ---
> scripts/gdb/linux/cpus.py | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/scripts/gdb/linux/cpus.py b/scripts/gdb/linux/cpus.py
> index 15fc4626d236..ce6703f1e35a 100644
> --- a/scripts/gdb/linux/cpus.py
> +++ b/scripts/gdb/linux/cpus.py
> @@ -173,6 +173,14 @@ def get_current_task(cpu):
> else:
> raise gdb.GdbError("Sorry, obtaining the current task is not allowed "
> "while running in userspace(EL0)")
> + elif utils.is_target_arch("riscv"):
> + current_task_addr = gdb.parse_and_eval("$tp")
> + if((current_task_addr.cast(utils.get_long_type()) >> 63) != 0):

Shouldn't there be a get_long_type().sizeof == 8 check somewhere before
shifting by 63? Or are 32-bit targets not supported at all for some
reason?

Thanks,
drew

> + current_task = current_task_addr.cast(task_ptr_type)
> + return current_task.dereference()
> + else:
> + raise gdb.GdbError("Sorry, obtaining the current task is not allowed "
> + "while running in userspace")
> else:
> raise gdb.GdbError("Sorry, obtaining the current task is not yet "
> "supported with this arch")
> --
> 2.25.1
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@xxxxxxxxxxxxxxxxxxx
> http://lists.infradead.org/mailman/listinfo/linux-riscv