From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84403 invoked by alias); 1 Mar 2018 13:04:47 -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 84107 invoked by uid 89); 1 Mar 2018 13:04:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*F:U*paul, Cloud, H*R:D*net X-HELO: gproxy6-pub.mail.unifiedlayer.com Received: from gproxy6-pub.mail.unifiedlayer.com (HELO gproxy6-pub.mail.unifiedlayer.com) (67.222.39.168) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Mar 2018 13:04:45 +0000 Received: from cmgw2 (unknown [10.0.90.83]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 036E71E0794 for ; Thu, 1 Mar 2018 06:04:44 -0700 (MST) Received: from box5008.bluehost.com ([50.116.64.19]) by cmgw2 with id Gd4g1x01K0QvKlu01d4jtf; Thu, 01 Mar 2018 06:04:43 -0700 X-Authority-Analysis: v=2.2 cv=M5g9E24s c=1 sm=1 tr=0 a=gch/BGY/Gm5DEW28s2kmlQ==:117 a=gch/BGY/Gm5DEW28s2kmlQ==:17 a=IkcTkHD0fZMA:10 a=v2DPQv5-lfwA:10 a=N4saNtO5jK8xaUqazrsA:9 a=QEXdDO2ut3YA:10 Received: from pool-74-104-137-100.bstnma.fios.verizon.net ([74.104.137.100]:59958 helo=homebase) by box5008.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1erNt2-002Qm6-IQ for gdb@sourceware.org; Thu, 01 Mar 2018 06:04:40 -0700 Message-ID: <1519909479.3684.41.camel@mad-scientist.net> Subject: gdbserver with a core file? From: Paul Smith Reply-To: paul@mad-scientist.net To: gdb@sourceware.org Date: Thu, 01 Mar 2018 13:04:00 -0000 Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BWhitelist: no X-Exim-ID: 1erNt2-002Qm6-IQ X-Source-Sender: pool-74-104-137-100.bstnma.fios.verizon.net (homebase) [74.104.137.100]:59958 X-Source-Auth: paul@mad-scientist.us X-Email-Count: 1 X-Source-Cap: bWFkc2NpZTE7bWFkc2NpZTE7Ym94NTAwOC5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-SW-Source: 2018-03/txt/msg00001.txt.bz2 Has anyone every considered, or actually implemented, the ability to use gdbserver to debug a core file remotely in addition to debugging live processes? More and more I'm seeing core files dumped on AWS or Google Cloud instances. It's really expensive (and slow!!) to copy these many-GB cores back to my local system for debugging, and they're often only needed for an hour or so. Of course I could debug them in the cloud, but either I need to go without source code during debugging or I need to copy my source code into the cloud, neither of which is particularly appealing for all kinds of reasons. When I was working on embedded systems gdbserver was a lifesaver, and it would save me a lot of time (and $$) if I could debug core files with it. Any thoughts on this?