From: Pedro Alves <palves@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA-v2] Fix PR 16201: internal error on a cygwin program linked against a DLL with no .data section
Date: Mon, 06 Jan 2014 18:34:00 -0000 [thread overview]
Message-ID: <52CAF71D.3050008@redhat.com> (raw)
In-Reply-To: <52b76e14.8886420a.29e6.ffffddb2SMTPIN_ADDED_BROKEN@mx.google.com>
Hi Pierre,
Sorry for the slow reply. Been away on vacation.
On 12/22/2013 10:55 PM, Pierre Muller wrote:
> @@ -455,17 +458,34 @@ read_pe_exported_syms (struct objfile *objfile)
> unsigned long characteristics = pe_get32 (dll, secptr1 + 36);
> char sec_name[SCNNMLEN + 1];
> int sectix;
> + unsigned int bfd_section_index;
> + asection *section;
>
> bfd_seek (dll, (file_ptr) secptr1 + 0, SEEK_SET);
> bfd_bread (sec_name, (bfd_size_type) SCNNMLEN, dll);
> sec_name[SCNNMLEN] = '\0';
>
> sectix = read_pe_section_index (sec_name);
> + section = bfd_get_section_by_name (dll, sec_name);
Can't coff have sections with duplicate names? If so,
then it'd be better to match the section some other way,
I guess by address?
> + if (section)
> + bfd_section_index = section->index;
> + else
> + bfd_section_index = -1;
>
> if (sectix != PE_SECTION_INDEX_INVALID)
> {
> section_data[sectix].rva_start = vaddr;
> section_data[sectix].rva_end = vaddr + vsize;
> + /* For .text, .data and .bss section
> + set corresponding sect_index_XXX,
> + even if it was already set before. */
> + if (sectix == PE_SECTION_INDEX_TEXT)
> + objfile->sect_index_text = sectix;
> + if (sectix == PE_SECTION_INDEX_DATA)
> + objfile->sect_index_data = sectix;
> + if (sectix == PE_SECTION_INDEX_BSS)
> + objfile->sect_index_bss = sectix;
> + section_data[sectix].index = bfd_section_index;
Do you still need this part?
> }
--
Pedro Alves
next prev parent reply other threads:[~2014-01-06 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 10:50 [PING RFA] " Pierre Muller
2013-12-11 17:02 ` Joel Brobecker
2013-12-13 21:40 ` [RFA-v2] " Pierre Muller
2013-12-18 3:55 ` Joel Brobecker
[not found] ` <52ab7ec0.c8da420a.12c6.ffffb3f4SMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-20 18:19 ` Pedro Alves
2013-12-22 22:56 ` Pierre Muller
[not found] ` <15250.2735647888$1387752987@news.gmane.org>
2013-12-23 2:31 ` asmwarrior
[not found] ` <52b76e14.8886420a.29e6.ffffddb2SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-06 18:34 ` Pedro Alves [this message]
2014-01-07 11:15 ` [RFA-v3] " Pierre Muller
[not found] ` <52cbe1c5.67ed440a.67e6.7288SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-07 20:58 ` Pedro Alves
2014-01-07 23:40 ` [COMMIT-v4] " Pierre Muller
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=52CAF71D.3050008@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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