2015-05-27 05:59:27

by Thiébaud Weksteen

[permalink] [raw]
Subject: scripts/gdb: multi arch lx_current

Hi Jan,

I've been working on lx_current and cpus.py to support other architectures
than just x86. From my understanding, current/get_current are not available
with the default debug option (-g). We could either modify that level so that
the inline functions/macros are available or reimplement part of logic to
retrieve the current task (sp masking, etc).

Are there any other options to retrieve the current task? What do you
recommend?

Thiebaud


2015-07-21 20:48:25

by Jan Kiszka

[permalink] [raw]
Subject: Re: scripts/gdb: multi arch lx_current

Hi Thiebaud,

sorry, just realized that this fell through the cracks after vacation
back then.

On 2015-05-27 05:29, Thiébaud Weksteen wrote:
> Hi Jan,
>
> I've been working on lx_current and cpus.py to support other architectures
> than just x86. From my understanding, current/get_current are not available
> with the default debug option (-g). We could either modify that level so that
> the inline functions/macros are available or reimplement part of logic to
> retrieve the current task (sp masking, etc).
>
> Are there any other options to retrieve the current task? What do you
> recommend?

I would prefer the reimplementation like we do elsewhere already.
Debugging should remain minimal invasive to the kernel.

Jan


Attachments:
signature.asc (181.00 B)
OpenPGP digital signature