linux-kernel - Re: [RFC PATCH] scripts/gdb: add data window feature

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 for Android: free password hash cracker in your pocket

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

Message-ID: <55AEB3CA.9090107@web.de>
Date:	Tue, 21 Jul 2015 23:04:10 +0200
From:	Jan Kiszka <jan.kiszka@....de>
To:	Houcheng Lin <houcheng@...il.com>, corbet@....net
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] scripts/gdb: add data window feature

On 2015-07-16 17:58, Houcheng Lin wrote:
> Add data window feature to show current kernel status
> on separate consoles, including: 1) registers, 2) back
> trace and 3) watch data windows.
> 
> The data window would help kernel developer to understand
> current hardware/ kernel status, and on single-stepping, the
> modified fields in the data window would be highlighted.

I was trying to get an overview of this feature. Unfortunately, it does
not work for me. I type in the commands you describe in the
documentation, but nothing shows up. I suspect there are some hard-coded
assumption about directory layouts etc. that aren't fulfilled here
(out-of-tree build).

Anyway, let's try to understand what you would like to achieve. This
seems to be some add-on tool for gdb debugging sessions to display
target states continuously in separate terminals. Right? Is this
comparable to gdb's tui mode?

More important, is this specific to the debugging infrastructure we have
in scripts/gdb? Or could I install it (after some modifications, I
guess) in my home directory and use it for any gdb session, not just
with Linux kernels? Is there anything in it that particularly refers to
Linux structures? In that case I would suggest to make it stand-alone
first so that one could easily include it whenever needed, either
explicitly or via ~/.gitinit.

Thanks for sharing in any case!

Jan

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