From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: N_DATA symbols are always in the .data section
Date: Fri, 12 Sep 2003 22:51:00 -0000 [thread overview]
Message-ID: <vt21xuloc61.fsf@zenia.home> (raw)
This reverts part of my last patch to dbxread.c.
2003-09-09 Jim Blandy <jimb@redhat.com>
* dbxread.c (read_dbx_symtab): The N_DATA and N_DATA | N_EXT
symbol types are, by definition, in the .data section, so it is
correct to use SECT_OFF_DATA (objfile) here, not data_sect_index.
If there is no .data section, there should be no N_DATA or N_DATA
| N_EXT symbols.
*** dbxread.c.~1.49.~ 2003-09-08 14:03:37.000000000 -0500
--- dbxread.c 2003-09-09 14:54:34.000000000 -0500
***************
*** 1409,1415 ****
case N_DATA | N_EXT:
case N_NBDATA | N_EXT:
! nlist.n_value += ANOFFSET (objfile->section_offsets, data_sect_index);
goto record_it;
case N_BSS:
--- 1409,1415 ----
case N_DATA | N_EXT:
case N_NBDATA | N_EXT:
! nlist.n_value += ANOFFSET (objfile->section_offsets, SECT_OFF_DATA (objfile));
goto record_it;
case N_BSS:
***************
*** 1476,1482 ****
continue;
case N_DATA:
! nlist.n_value += ANOFFSET (objfile->section_offsets, data_sect_index);
goto record_it;
case N_UNDF | N_EXT:
--- 1476,1482 ----
continue;
case N_DATA:
! nlist.n_value += ANOFFSET (objfile->section_offsets, SECT_OFF_DATA (objfile));
goto record_it;
case N_UNDF | N_EXT:
reply other threads:[~2003-09-12 22:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vt21xuloc61.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@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