From: Joel Brobecker <brobecker@adacore.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Fix qOffsets handling
Date: Fri, 21 Sep 2007 22:19:00 -0000 [thread overview]
Message-ID: <20070921221937.GB3963@adacore.com> (raw)
In-Reply-To: <m3wsuj8ywc.fsf@codesourcery.com>
> Daniel Jacobowitz has approved this change off-list, and asked me to
> suggest it be included on the 6.7 branch as well. I'll wait for
> further comments here, and commit to trunk on Monday; Joel, is this
> okay for the branch?
Sure! I agree it should be applied to the branch as well.
>
> gdb/ChangeLog:
> 2007-09-21 Jim Blandy <jimb@codesourcery.com>
>
> * symfile.h (struct symfile_segment_data): Doc fixes.
> * symfile.c (symfile_map_offsets_to_segments): Doc fixes.
> Assert that we were passed some loaded segment addresses,
> and that sections' segment numbers are valid.
> Simplify offset calculation.
> * remote.c (get_offsets): Clarify selection of relocate-by-segment
> strategy, and set num_segments correctly. Delete redundant
> assignments to do_sections.
Thanks,
--
Joel
next prev parent reply other threads:[~2007-09-21 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 21:57 Jim Blandy
2007-09-21 22:19 ` Joel Brobecker [this message]
2007-09-24 21:49 ` Jim Blandy
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=20070921221937.GB3963@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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