From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41267 invoked by alias); 13 Mar 2019 15:41:51 -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 41259 invoked by uid 89); 13 Mar 2019 15:41:50 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=BAYES_20,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,SPF_SOFTFAIL autolearn=no version=3.3.1 spammy=H*r:TLS1.0, HX-Spam-Relays-External:4864, H*r:f8b0, HX-Spam-Relays-External:2607 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Mar 2019 15:41:49 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:48656) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h460p-0008GD-MD for gdb@sourceware.org; Wed, 13 Mar 2019 11:41:47 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57902) by fencepost.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h460n-0003hT-Bz for gdb@gnu.org; Wed, 13 Mar 2019 11:41:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h460l-0008Do-Ur for gdb@gnu.org; Wed, 13 Mar 2019 11:41:45 -0400 Received: from mail-it1-x134.google.com ([2607:f8b0:4864:20::134]:39130) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h460l-0008DN-JA for gdb@gnu.org; Wed, 13 Mar 2019 11:41:43 -0400 Received: by mail-it1-x134.google.com with SMTP id l15so3574140iti.4 for ; Wed, 13 Mar 2019 08:41:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7tmyJkubGv2515B1w3hmRZ6ornnaVhq/y2nT84VuLR0=; b=DqElhCQKIwAFNyhAylcuL8j9ctewQtf9yy4jy5St3NvDLZ6jS1vDQVv3K1RcM0+xQC fTAgbXwJI9BZIYlQ79Mjjnfb8VtK+DWcbV4k3AUcLZVe5edYyC+vbprkqFHIqGw1lH9e DSEIIU3RtY/sRRAxuNX26i0ib9y9K/b8KeJVUJQJYLQ4vnHW2MDXOc5ZiZCclj6KUOqQ p+bYBVqPA251JMxgTp8VYfS3PGOiB0fg3iLmpEv7TOjq6zFnNCJFjviS8M4ay5OYJSb4 8aVxoo831KD0EFJzGdmsSNHXEdDG0FSat8IuUwpdIq8RyPQLXVB6e3fX1kO1j28z/hAT DfTg== MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Jirka_Koutn=C3=BD?= Date: Wed, 13 Mar 2019 15:41:00 -0000 Message-ID: Subject: Re: question about why gdb needs executable's binary To: Andreas Schwab Cc: gdb@gnu.org X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::134 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-SW-Source: 2019-03/txt/msg00025.txt.bz2 Thanks Andreas! Aha that's interesting.. hmm so, is there some read-only segment, that would contain information necessary for the output of 'where'? Den ons. 13. mar. 2019 kl. 14:34 skrev Andreas Schwab : > On M=C3=A4r 13 2019, Jirka Koutn=C3=BD wrote: > > > If we assume debugging a core file generated by an excutable with > stripped > > symbols (that gdb is able to find and load correctly in my case), > > I was wondering why does gdb still need the executable's binary as > > well? > > A core file only contains data from modified mappings. Any data from > read-only mappings needs to be read from the original files. > > Andreas. > > -- > Andreas Schwab, SUSE Labs, schwab@suse.de > GPG Key fingerprint =3D 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 > "And now for something completely different." >