From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Linas Vepstas (Code Aurora)" Subject: Re: [patch v3 19/36] Hexagon: Add ptrace support Date: Fri, 9 Sep 2011 16:18:08 -0500 Message-ID: <20110909211808.GA3150@codeaurora.org> References: <20110909010847.294039464@codeaurora.org> <20110909010916.525482401@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]:24978 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758767Ab1IIVST (ORCPT ); Fri, 9 Sep 2011 17:18:19 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Jonas Bonn Cc: Richard Kuo , linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org, arnd@arndb.de On Fri, Sep 09, 2011 at 10:15:20PM +0200, Jonas Bonn wrote: > > That said, I don't think gdbserver has been updated to use > GETREGSET/SETREGSET. This is a bit like the uClibc/glibc issue, Some dumb questions then: I notice that a few arches declare struct user_regs_struct in glibc, most of the others in the kernel. If I were to make pt_regs completely kernel-private, then I really do need to have struct user_regs_struct declared the kernel headers, right? Putting a printk into case PTRACE_POKEUSR seemed to show that gdb was using this (and was somehow mis-numbering the registers ... sigh.) Are you saying that the default should handle this? --linas -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.