From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix PR 16201: internal error on a cygwin program linked against a DLL with no .data section
Date: Mon, 02 Dec 2013 03:30:00 -0000 [thread overview]
Message-ID: <20131202033043.GP3114@adacore.com> (raw)
In-Reply-To: <007101ceebd1$3d2bb590$b78320b0$@muller@ics-cnrs.unistra.fr>
> See discussion in
> https://sourceware.org/bugzilla/show_bug.cgi?id=16201
>
> The patch below seems to fix the issues as it avoids calling
> prim_record_minimal_symbol
> with ms_type argument being equal to mst_XXX (where XXX can be text, data or
> bss)
> without having set sect_index_XXX field of the corresponding objfile.
>
> Is this OK?
>
> Pierre Muller
>
>
> 2013-11-27 Pierre Muller <muller@sourceware.org>
>
> PR 16201
> coff-pe-read.c (read_pe_exported_syms): Set sect_index_text,
> sect_index_data and sect_index_bss of objfile struct, even if
> there is no canonical '.text', '.data' or '.bss' named section.
I am unsure about this patch, at the moment. But is it a regression,
and if yes, should be listed as a must-have for 7.7? If yes again,
let's have it added to the release wiki page:
https://sourceware.org/gdb/wiki/GDB_7.7_Release
Thank you!
> diff --git a/gdb/coff-pe-read.c b/gdb/coff-pe-read.c
> index 91ee3f6..954c457 100644
> --- a/gdb/coff-pe-read.c
> +++ b/gdb/coff-pe-read.c
> @@ -466,6 +466,13 @@ read_pe_exported_syms (struct objfile *objfile)
> {
> section_data[sectix].rva_start = vaddr;
> section_data[sectix].rva_end = vaddr + vsize;
> + /* Force sect_index, 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;
> }
> else
> {
> @@ -480,11 +487,23 @@ read_pe_exported_syms (struct objfile *objfile)
> section_data[otherix].rva_end = vaddr + vsize;
> section_data[otherix].vma_offset = 0;
> if (characteristics & IMAGE_SCN_CNT_CODE)
> - section_data[otherix].ms_type = mst_text;
> + {
> + section_data[otherix].ms_type = mst_text;
> + if (objfile->sect_index_text == -1)
> + objfile->sect_index_text = otherix;
> + }
> else if (characteristics & IMAGE_SCN_CNT_INITIALIZED_DATA)
> - section_data[otherix].ms_type = mst_data;
> + {
> + section_data[otherix].ms_type = mst_data;
> + if (objfile->sect_index_data == -1)
> + objfile->sect_index_data = otherix;
> + }
> else if (characteristics & IMAGE_SCN_CNT_UNINITIALIZED_DATA)
> - section_data[otherix].ms_type = mst_bss;
> + {
> + section_data[otherix].ms_type = mst_bss;
> + if (objfile->sect_index_bss == -1)
> + objfile->sect_index_bss = otherix;
> + }
> else
> section_data[otherix].ms_type = mst_unknown;
> otherix++;
--
Joel
next prev parent reply other threads:[~2013-12-02 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 1:23 Pierre Muller
2013-12-02 3:30 ` Joel Brobecker [this message]
2013-12-02 10:44 ` Pierre Muller
2013-12-02 11:37 ` Joel Brobecker
2013-12-02 14:04 ` Pierre Muller
2013-12-02 14:10 ` Joel Brobecker
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=20131202033043.GP3114@adacore.com \
--to=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