Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Smith, Stephen \(SWCOE\)" <Stephen.Smith@honeywell.com>
To: "Daniel Jacobowitz" <drow@false.org>,
		"General GDB Mailing List" <gdb@sourceware.org>
Subject: RE: GDB solib interface
Date: Sun, 17 Dec 2006 00:42:00 -0000	[thread overview]
Message-ID: <EF244E26469B2C42B2B72AC465843D6B03C957DB@AZ18EV808.global.ds.honeywell.com> (raw)
In-Reply-To: <20061208211922.GA28061@nevyn.them.org>

The function solib_target_relocate_section_addresses() refers to
functions and datamembers that no longer exist.  I believe that
borrowing code from the svr4 code is the correct thing to do.

Can anyone confirm that that is the right thing?


-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Friday, December 08, 2006 2:19 PM
To: Smith, Stephen (SWCOE); General GDB Mailing List
Subject: Re: GDB solib interface

+static void
+solib_target_free_so (struct so_list *so)
+{
+  xfree (so->lm_info);
+}
+
+static void
+solib_target_relocate_section_addresses (struct so_list *so,
+					 struct section_table *sec)
+{
+  int flags = bfd_get_section_flags (sec->bfd, sec->the_bfd_section);
+  CORE_ADDR offset;
+
+  offset = symfile_section_offset_from_segment (sec->bfd,
sec->the_bfd_section,
+						so->lm_info->textSeg,
+						so->lm_info->dataSeg);
+


  parent reply	other threads:[~2006-12-17  0:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 22:12 Smith, Stephen (SWCOE)
2006-12-04 22:25 ` Michael Snyder
2006-12-04 22:29   ` Daniel Jacobowitz
2006-12-04 22:28 ` Daniel Jacobowitz
2006-12-04 22:48   ` Smith, Stephen (SWCOE)
2006-12-04 23:48     ` Michael Snyder
2006-12-05  2:09       ` Smith, Stephen (SWCOE)
2006-12-05 23:03   ` Smith, Stephen (SWCOE)
2006-12-08 21:19   ` Daniel Jacobowitz
2006-12-08 22:23     ` Smith, Stephen (SWCOE)
2006-12-08 23:21       ` Daniel Jacobowitz
2006-12-15 21:12     ` Smith, Stephen (SWCOE)
2006-12-15 22:39       ` Daniel Jacobowitz
2006-12-17  0:42     ` Smith, Stephen (SWCOE) [this message]
2006-12-17  2:16       ` Daniel Jacobowitz
2006-12-17  6:37         ` Stephen & Linda Smith
2006-12-17 15:24           ` Daniel Jacobowitz
2006-12-29 22:08         ` Stephen & Linda Smith
2006-12-29 22:54           ` Stephen & Linda Smith
2007-01-04 20:37     ` Smith, Stephen (SWCOE)
2007-01-04 20:38       ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2007-01-04 21:32 Smith, Stephen (SWCOE)
2007-01-04 21:40 ` Daniel Jacobowitz
2007-01-04 21:46   ` Smith, Stephen (SWCOE)
2007-01-04 21:49     ` Daniel Jacobowitz
2007-01-05  3:39       ` Stephen & Linda Smith
2007-01-05  3:48         ` Daniel Jacobowitz
     [not found]           ` <EF244E26469B2C42B2B72AC465843D6B03E34F88@AZ18EV808.global.ds.honeywell.com>
2007-01-05  4:01             ` Daniel Jacobowitz
2007-01-05 19:26               ` Smith, Stephen (SWCOE)
2007-02-07 19:41                 ` Smith, Stephen (SWCOE)
2007-02-07 23:57                   ` Smith, Stephen (SWCOE)
2006-12-04 21:55 Smith, Stephen (SWCOE)
2006-12-04 21:57 ` Daniel Jacobowitz

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=EF244E26469B2C42B2B72AC465843D6B03C957DB@AZ18EV808.global.ds.honeywell.com \
    --to=stephen.smith@honeywell.com \
    --cc=drow@false.org \
    --cc=gdb@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