From: Daniel Jacobowitz <drow@mvista.com>
To: Lucy Zhang <lucyz@uclink4.berkeley.edu>
Cc: gdb@sources.redhat.com
Subject: Re: missing text segment in Elf dump
Date: Thu, 15 Aug 2002 12:29:00 -0000 [thread overview]
Message-ID: <20020815193009.GA8816@nevyn.them.org> (raw)
In-Reply-To: <003301c24489$e8206280$9a0a0109@zhangl>
On Thu, Aug 15, 2002 at 11:30:56AM -0700, Lucy Zhang wrote:
> Can you elaborate on how GDB gets it from the application? and by
> application do you mean the executable file?
Yes. They are both ELF binaries with mapped sections. GDB can read
data directly from the application; and the kernel generally will not
dump it.
> 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
No, this has nothing to do with segments, only with debug information.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-08-15 19:29 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
2002-08-15 12:29 ` Daniel Jacobowitz [this message]
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=20020815193009.GA8816@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=lucyz@uclink4.berkeley.edu \
/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