From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 90506 invoked by alias); 28 Sep 2016 15:02: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 90486 invoked by uid 89); 28 Sep 2016 15:02:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:ru X-HELO: mx5.ptsecurity.com Received: from mx5.ptsecurity.com (HELO mx5.ptsecurity.com) (45.58.112.35) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 28 Sep 2016 15:02:44 +0000 Received: from dc1-mail-01.ptsecurity.ru (10.0.52.111) by ny-mx-01.ptsecurity.ru (10.6.20.6) with Microsoft SMTP Server (TLS) id 15.1.466.34; Wed, 28 Sep 2016 18:02:42 +0300 Received: from [10.0.72.136] (10.0.72.136) by dc1-mail-01.ptsecurity.ru (10.0.52.111) with Microsoft SMTP Server (TLS) id 15.1.466.34; Wed, 28 Sep 2016 18:02:40 +0300 Subject: Re: Custom core file References: To: From: Nikolay Martyanov Message-ID: Date: Wed, 28 Sep 2016 15:02:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: dc1-mail-01.ptsecurity.ru (10.0.52.111) To dc1-mail-01.ptsecurity.ru (10.0.52.111) X-SW-Source: 2016-09/txt/msg00068.txt.bz2 Thanks for response! > Then in the same python script execute dump/restore commands to load these into memory I have tried to use "dump/restore" approach, but there is an issue. When you use a restore command, you should already be in a context of debugging process. I tried it like this: 1. Run GDB 2. Load symbols with `file core.so` 3. Try to shove memory with `restore raw_mem.dump` After that I have message: `You can't do that without a process to debug.` So, I guess, dump/restore approach works only in two cases: a) debugging live process you have attached to (it's not my case, as I perform postmortem debug) b) already has loaded core file, which provides a context via saved CPU state - and it is the way I chose to follow. Am I wrong in my guesses? Thanks, Nikolay