linux-kernel - Re: scripts/gdb: multi arch lx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <55AEB00E.8000200@web.de>
Date:	Tue, 21 Jul 2015 22:48:14 +0200
From:	Jan Kiszka <jan.kiszka@....de>
To:	Thiébaud Weksteen <thiebaud@...steen.fr>
Cc:	linux-kernel@...r.kernel.org
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


Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)