From: Roland McGrath <roland@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: [patch] bfd: Core files with p_filesz < p_memsz (build-id)
Date: Sun, 29 Jul 2007 15:29:00 -0000 [thread overview]
Message-ID: <20070728201604.AEBDB4D058D@magilla.localdomain> (raw)
In-Reply-To: Jan Kratochvil's message of Saturday, 28 July 2007 21:13:54 +0200 <20070728191354.GA14892@host0.dyn.jankratochvil.net>
Are you sure that changing _bfd_elf_make_section_from_phdr is the right way
to fix gdb?
It is in a certain sense accurate to split the one segment into two
sections, a leading SEC_LOAD one and a trailing one without SEC_LOAD.
What does your change do to e.g. objcopy on a core file?
Thanks,
Roland
next prev parent reply other threads:[~2007-07-28 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 20:16 Jan Kratochvil
2007-07-29 12:30 ` Jan Kratochvil
2007-07-29 15:29 ` Roland McGrath [this message]
2007-07-29 18:32 ` Jan Kratochvil
2007-08-01 13:05 ` Alan Modra
2007-08-02 20:03 ` Daniel Jacobowitz
2007-08-03 0:13 ` Alan Modra
2007-08-03 0:21 ` Daniel Jacobowitz
2007-08-03 2:50 ` Alan Modra
2007-08-06 19:32 ` Daniel Jacobowitz
2007-08-09 16:04 ` Jan Kratochvil
2007-07-30 14:07 ` [resent] " Jan Kratochvil
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=20070728201604.AEBDB4D058D@magilla.localdomain \
--to=roland@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=jan.kratochvil@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).