Skip to contentSkip to conversation

scripts/gdb: multi arch lx_current

DISCUSSION Thiébaud Weksteen 2 participants 2 messages May 27, 2015 – Jul 21, 2015

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

Hi Thiebaud,

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

Quoted 10 lines · Thiébaud Weksteen

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