From: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: missing text segment in Elf dump
Date: Thu, 15 Aug 2002 11:27:00 -0000 [thread overview]
Message-ID: <003301c24489$e8206280$9a0a0109@zhangl> (raw)
In-Reply-To: <20020815180824.GA4211@nevyn.them.org>
Can you elaborate on how GDB gets it from the application? and by
application do you mean the executable file?
Also, when I try to look at the source code using "list", does this have
anything to do with the text segment? I ask because it would work for some
source files and not for others. i.e.
(gdb) list condvar.c:88
83 condvar.c: No such file or directory.
in condvar.c
thank you,
Lucy
----- Original Message -----
From: "Daniel Jacobowitz" <drow@mvista.com>
To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
Cc: <gdb@sources.redhat.com>
Sent: Thursday, August 15, 2002 11:08 AM
Subject: Re: missing text segment in Elf dump
> On Thu, Aug 15, 2002 at 11:10:12AM -0700, Lucy Zhang wrote:
> > Hi,
> >
> > When GDB is debugging an ELF core dump, what is it use for the text
segment.
> > I realized in the Elf core that I've created from another dump file,
that
> > the text segment is cut off because the size is too big. The actual text
> > segment spans 0x8048000 - 0x98cc4e0, but I only included the first 8MB
of
> > the area in the ELF dump. So I'm wondering what affects will this have
on
> > GDB? what kind of information will be missing due to the incomplete text
> > segment?
>
> Most ELF core dumps don't even include the text segment. GDB gets it
> from the application instead, and only writeable segments are in the
> core file...
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-15 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 11:06 Lucy Zhang
2002-08-15 11:08 ` Daniel Jacobowitz
2002-08-15 11:27 ` Lucy Zhang [this message]
2002-08-15 12:29 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003301c24489$e8206280$9a0a0109@zhangl' \
--to=lucyz@uclink4.berkeley.edu \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox