From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83553 invoked by alias); 13 Oct 2017 18:00:37 -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 83523 invoked by uid 89); 13 Oct 2017 18:00:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*r:sk:gdb@sou, rom, ROM, H*c:alternative X-HELO: mail-it0-f47.google.com Received: from mail-it0-f47.google.com (HELO mail-it0-f47.google.com) (209.85.214.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 13 Oct 2017 18:00:33 +0000 Received: by mail-it0-f47.google.com with SMTP id j140so11517583itj.1 for ; Fri, 13 Oct 2017 11:00:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=/OZlA/i/tfsNUc10nautsgsZ6b/b619k46vI/nX7sxg=; b=bArMt1/D8ZpV85NQ3D9RPz7i7dzOidZpdNxv5SoHJrCJm9A9EtOm3SxKiIwQyT4v7U D7ueT7Otfd7wyBztpxvCTJCTP2PoeMzDYGbqH4HmBrFy8c5zWJ7tCUbRJyZWXqanzSue quMudRuBLKcfDR6NMWBbfT7FaBCye52p1VZLbjPajU1276pYSFE8zqBDksSarLDl6bJA dzW3gyfZMSChpWkJ1WTIk0vTPeO+xArBBVfNlpflT+Ls8XpZ/8ICjl5egexqDiUY9uzG aC1bC/cNTj6hs9f+rxWX+TsKVrEGv5G6r9bkk4Y1O7y8m0zrvp2CfXxiFqBZyxzNyiDP bCsg== X-Gm-Message-State: AMCzsaUmlRlVqlVfz/10XLWXCfFMUKYGwicSF4WVD9jcftkSRNtlMJvF w8A3fdYQNgI61yXePD/dbTUdedzv3d/5xL2rzvA= X-Google-Smtp-Source: ABhQp+QbQENvjn2rPoUMaoQESx9LVzZ5pkbdNhw0n0pshD88VLnJIK3hS/evViMQW6rjgVnaIJFzF21cMwZmO0na9jI= X-Received: by 10.36.179.15 with SMTP id e15mr3410392itf.77.1507917631232; Fri, 13 Oct 2017 11:00:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.33.146 with HTTP; Fri, 13 Oct 2017 11:00:30 -0700 (PDT) In-Reply-To: References: From: Hesham M Date: Fri, 13 Oct 2017 18:00:00 -0000 Message-ID: Subject: Re: Postmortem debugging with arm-none-eabi-gdb from memory dump (not core) To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2017-10/txt/msg00036.txt.bz2 Hi, I'm still looking for guidance or pointers that may help with this issue. Thanks, -Hesham On Thu, Oct 5, 2017 at 5:55 AM, Hesham M wrote: > Hi all, > > As this is my first email to the list, and as an old user for gdb, I'd > like first to thank the gdb community for their effort. > > In a bare-metal ARM system, is there a way to use arm-none-eabi-gdb for > postmortem debugging, the same way we do when we debug with core file on > Linux, for example? > > The issue is that I don't have a "core" file but I can generate memory > dump of the whole memory (ROM is already known and through the hardware > debugger used I can write the RAM contents to a file (outside the target of > course). I can also collect the registers at the time of the crash. I can > do the debugging/analysis if I connect gdb to the target at the time of the > crash but I need to do this in later time away from the target. I hope to > find a way to debug with memory dumps the same way gdb debugs with core > files. > > Of course if I can convert the memory dump to a valid core file, it might > be another path to the solution. I don't know how to do that or if there is > a tool that can help with this conversion. > > Any idea if this is possible? > > A variant of this is idea is done for Keil tools: > https://os.mbed.com/blog/entry/Post-mortem-debugging-with-ARM-mbed/ > > I have posted a similar question on stackoverflow but they closed it! So, > please let me know if my question isn't clear. > > Thanks, > -Hesham >