From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76920 invoked by alias); 28 Sep 2016 14:58:56 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 76902 invoked by uid 89); 28 Sep 2016 14:58:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Martyanov, martyanov X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 28 Sep 2016 14:58:54 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 78769B5C2C; Wed, 28 Sep 2016 14:58:53 +0000 (UTC) Received: from host1.jankratochvil.net (ovpn-116-55.ams2.redhat.com [10.36.116.55]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u8SEwoYk015678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Sep 2016 10:58:52 -0400 Date: Wed, 28 Sep 2016 14:58:00 -0000 From: Jan Kratochvil To: Nikolay Martyanov Cc: gdb@sourceware.org Subject: Re: Custom core file Message-ID: <20160928145850.GA20365@host1.jankratochvil.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.0 (2016-08-17) X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00067.txt.bz2 On Wed, 28 Sep 2016 15:31:12 +0200, Nikolay Martyanov wrote: > I have a self-written bare-metal hypervisor for x86 arch and I'd like to > perform postmortem debugging of it's core (not VM, hypervisor itself!). > So the idea is to save physical memory state and later use GDB to interpret > it. I still do not understand what is the goal. "not VM, hypervisor itself!" would say that running "/usr/bin/gcore "+getpid() on the hypervisor process would do the job. But then "the idea is to save physical memory state" would suggest me you want to dump the guest VM - like what guest kdump does or what is in guest Linux kernel /proc/kcore (where it is without the physical memory). Jan