| 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
| ||
|
Date: Wed, 09 Jun 2010 19:50:46 +0100 From: David Howells <dhowells@...hat.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: dhowells@...hat.com, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] FRV: Implement the GDB remote protocol 'p' command to retrieve a register Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > Implement the GDB remote protocol 'p' command to retrieve a single register > > value. > > Is there any value to this? Apparently it used to work just because that > command never did anything (rather than return an error). Why not just > reinstate that behavior instead? That's a reasonable argument. The 'p' command would be more efficient if gdb uses it when required to get single values, but once it has decided to use the 'g' command, it seems to stick with it. > There's doesn't seem to be any reason to implement the single-register > case unless there is some legacy use of it. There's a good reason gdb > tends to use the "register block" thing, and it tends to be easier to > implement too (no crazy case statements etc). It's slower to use 'g', however, if we only want the value in one register, and I'm usually doing gdb protocol over serial. However, as stated above, once it's decided to use 'g', gdb doesn't seem to want to use 'p' any more. David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists