public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: amodra@bigpond.net.au
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: elf.c assign_file_positions_for_segments
Date: Fri, 24 Sep 2004 06:36:00 -0000	[thread overview]
Message-ID: <200409240635.i8O6Zptk010379@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20040924030920.GG30257@bubble.modra.org> (message from Alan Modra on Fri, 24 Sep 2004 12:39:20 +0930)

   Date: Fri, 24 Sep 2004 12:39:20 +0930
   From: Alan Modra <amodra@bigpond.net.au>

   On Fri, Sep 24, 2004 at 09:47:57AM +0930, Alan Modra wrote:
   > If we really don't need the SEC_HAS_CONTENTS test, then I'll take it out
   > and gdb gcore should be OK, otherwise I might ask you to clear
   > SEC_HAS_CONTENTS in gdb.

   I think it likely that the SEC_HAS_CONTENTS test is just a hack to work
   around another problem.  I'm applying the following to go back to the
   old behaviour.

Thanks.

   You might like to clear SEC_HAS_CONTENTS in gdb too, as it will result
   in needless file space being allocated.

I'll investigate this.  Can't say I completely understand what's
happening here, but I can always bother Michael Snyder with it, since
he wrote the initial gcore code.

Cheers,

Mark

  reply	other threads:[~2004-09-24  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 15:51 Mark Kettenis
2004-09-23 23:42 ` Alan Modra
2004-09-24  0:18   ` Alan Modra
2004-09-24  3:09     ` Alan Modra
2004-09-24  6:36       ` Mark Kettenis [this message]
2004-09-28 16:15 Michael Chastain

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=200409240635.i8O6Zptk010379@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).