From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [commit] mn10300-linux: Add shared library support
Date: Wed, 07 Sep 2005 00:29:00 -0000 [thread overview]
Message-ID: <20050906172738.5d00e761@ironwood.lan> (raw)
In-Reply-To: <20050907000613.GA18692@nevyn.them.org>
On Tue, 6 Sep 2005 20:06:13 -0400
Daniel Jacobowitz <drow@false.org> wrote:
> May I recommend svr4_ilp32_fetch_link_map_offsets instead?
Yes, thanks! I've just committed the following change:
* mn10300-linux-tdep.c (mn10300_linux_svr4_fetch_link_map_offsets):
Delete.
(am33_linux_init_osabi): Register svr4_ilp32_fetch_link_map_offsets
instead.
Index: mn10300-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mn10300-linux-tdep.c,v
retrieving revision 1.2
diff -u -p -r1.2 mn10300-linux-tdep.c
--- mn10300-linux-tdep.c 6 Sep 2005 23:14:44 -0000 1.2
+++ mn10300-linux-tdep.c 7 Sep 2005 00:22:03 -0000
@@ -468,49 +468,6 @@ am33_regset_from_core_section (struct gd
am33_collect_gregset_method);
}
-/* Fetch, and possibly build, an appropriate link_map_offsets structure
- for mn10300 linux targets using the struct offsets defined in <link.h>.
- Note, however, that link.h is not actually referred to in this file.
- Instead, the relevant structs offsets were obtained from examining
- link.h. (We can't refer to link.h from this file because the host
- system won't necessarily have it, or if it does, the structs which
- it defines will refer to the host system, not the target.) */
-
-struct link_map_offsets *
-mn10300_linux_svr4_fetch_link_map_offsets (void)
-{
- static struct link_map_offsets lmo;
- static struct link_map_offsets *lmp = 0;
-
- if (lmp == 0)
- {
- lmp = &lmo;
-
- lmo.r_debug_size = 8; /* Actual size is 20, but this is all we
- need. */
-
- lmo.r_map_offset = 4;
- lmo.r_map_size = 4;
-
- lmo.link_map_size = 20; /* Might be larger, but this is all we
- need. */
-
- lmo.l_addr_offset = 0;
- lmo.l_addr_size = 4;
-
- lmo.l_name_offset = 4;
- lmo.l_name_size = 4;
-
- lmo.l_next_offset = 12;
- lmo.l_next_size = 4;
-
- lmo.l_prev_offset = 16;
- lmo.l_prev_size = 4;
- }
-
- return lmp;
-}
-
/* AM33 Linux osabi has been recognized.
Now's our chance to register our corefile handling. */
@@ -520,7 +477,7 @@ am33_linux_init_osabi (struct gdbarch_in
set_gdbarch_regset_from_core_section (gdbarch,
am33_regset_from_core_section);
set_solib_svr4_fetch_link_map_offsets
- (gdbarch, mn10300_linux_svr4_fetch_link_map_offsets);
+ (gdbarch, svr4_ilp32_fetch_link_map_offsets);
}
void
next prev parent reply other threads:[~2005-09-07 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 23:18 Kevin Buettner
2005-09-07 0:06 ` Daniel Jacobowitz
2005-09-07 0:29 ` Kevin Buettner [this message]
2005-09-10 13:04 ` Mark Kettenis
2005-09-12 2:29 ` Kevin Buettner
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=20050906172738.5d00e761@ironwood.lan \
--to=kevinb@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