From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50724) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RG9Tq-0001BP-Iz for qemu-devel@nongnu.org; Tue, 18 Oct 2011 09:13:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RG9Tl-0006Hf-61 for qemu-devel@nongnu.org; Tue, 18 Oct 2011 09:13:18 -0400 Received: from david.siemens.de ([192.35.17.14]:19871) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RG9Tk-0006H5-PK for qemu-devel@nongnu.org; Tue, 18 Oct 2011 09:13:13 -0400 Message-ID: <4E9D7B64.3030408@siemens.com> Date: Tue, 18 Oct 2011 15:13:08 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E9D3804.5040000@cn.fujitsu.com> <4E9D3847.8040202@siemens.com> <4E9D3965.4090003@cn.fujitsu.com> <4E9D394E.6050907@siemens.com> <20111018083416.GL8872@amd.home.annexia.org> <4E9D3A80.10402@siemens.com> <4E9D3B29.5060207@siemens.com> <4E9D57C6.8040809@redhat.com> <20111018104257.GA24311@lst.de> <4E9D756B.7060509@siemens.com> <20111018130830.GA27797@lst.de> In-Reply-To: <20111018130830.GA27797@lst.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: Paolo Bonzini , Luiz Capitulino , qemu-devel , "Richard W.M. Jones" On 2011-10-18 15:08, Christoph Hellwig wrote: > On Tue, Oct 18, 2011 at 02:47:39PM +0200, Jan Kiszka wrote: >>>> Crash can also do live system analysis. :) >>> >>> crash in fact is gdb - with a lot of additional commands. >> >> Is there a trick to make it work against a gdbserver? > > No idea. I just noticed that crash was built around a gdb source > tree and additional files when I had to hack it for a new kernel > version a while ago. > > The optimum would be if all the crash changes were merged back > into upstream gdb, but I'm not sure the gdb community would like > to see all that very linux kernel specific code (especially given that it's > very version dependent) That's why I'm advocating gdb scripts, maybe maintained inside the kernel tree. But I need to look closer as well to see if vanilla gdb is already able to provide all registers used by crash so far (surely not all required for perfect debugging, but that's a long-known issue). Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux