public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM] archer-tromey-remove-obj_section: don't include SEC_DATA when looking for BSS section
Date: Tue, 22 Jan 2013 18:32:00 -0000 [thread overview]
Message-ID: <20130122183248.400.qmail@sourceware.org> (raw)
The branch, archer-tromey-remove-obj_section has been updated
via b8b2f2c2e750806306bbe43388a08aaff3952205 (commit)
from db6a28f95f3c29c838e2454d7e03f61b837649a7 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email.
- Log -----------------------------------------------------------------
commit b8b2f2c2e750806306bbe43388a08aaff3952205
Author: Tom Tromey <tromey@redhat.com>
Date: Tue Jan 22 11:32:32 2013 -0700
don't include SEC_DATA when looking for BSS section
-----------------------------------------------------------------------
Summary of changes:
gdb/somread.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
First 500 lines of diff:
diff --git a/gdb/somread.c b/gdb/somread.c
index 4dfecbb..806a8e6 100644
--- a/gdb/somread.c
+++ b/gdb/somread.c
@@ -485,7 +485,7 @@ som_symfile_offsets (struct objfile *objfile, struct section_addr_info *addrs)
&objfile->sect_index_text);
set_section_index (objfile, 0, SEC_ALLOC | SEC_DATA,
&objfile->sect_index_data);
- set_section_index (objfile, SEC_LOAD, SEC_ALLOC | SEC_DATA | SEC_LOAD,
+ set_section_index (objfile, SEC_LOAD, SEC_ALLOC | SEC_LOAD,
&objfile->sect_index_bss);
set_section_index (objfile, 0, SEC_ALLOC | SEC_READONLY,
&objfile->sect_index_rodata);
hooks/post-receive
--
Repository for Project Archer.
reply other threads:[~2013-01-22 18:32 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=20130122183248.400.qmail@sourceware.org \
--to=tromey@sourceware.org \
--cc=archer-commits@sourceware.org \
/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).