From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kris Warkentin" <kewarken@qnx.com>,
"Mark Kettenis" <kettenis@chello.nl>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] QNX Neutrino/i386 support
Date: Sat, 08 Mar 2003 15:22:00 -0000 [thread overview]
Message-ID: <006601c2e587$36c4d490$2a00a8c0@dash> (raw)
In-Reply-To: <005a01c2e586$c0178360$2a00a8c0@dash>
> > I'm still struggling with the shared library stuff. There's something
> > fishy in there, but it seems that the comment in nto-tdep.c is wrong,
> > or at least outdated.
>
> There have been some fairly long thread on the mailing list about the
solib
> issue. Look for threads 'relocation of shared libs not based at 0'
starting
> back in November/December and some more recently. You may be right about
> the comment - I should take a look at it again but the long and the short
of
> it is that we have a slightly different interpretation of the way
> relocations are done. Our chief architect can explain it better but it's
> possible that neither interpretation is wrong - one treats two base
> addresses as the same, the other doesn't. Either way, the override of
> relocate_section_addresses is ABSOLUTELY required. If this is not done,
> global data in shared objects will be off by a page.
Aha. Found relevant explanation from our chief architect.
http://sources.redhat.com/ml/gdb/2003-02/msg00202.html
cheers,
Kris
next prev parent reply other threads:[~2003-03-08 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 13:45 Mark Kettenis
2003-03-08 15:02 ` Kris Warkentin
2003-03-08 23:49 ` Mark Kettenis
2003-03-09 0:14 ` Mark Kettenis
2003-03-09 4:34 ` Kris Warkentin
2003-03-09 17:51 ` Kris Warkentin
2003-03-19 18:19 ` Kris Warkentin
2003-03-19 18:27 ` Mark Kettenis
2003-03-08 15:19 ` Kris Warkentin
2003-03-08 15:22 ` Kris Warkentin [this message]
2003-03-09 14:54 Kris Warkentin
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='006601c2e587$36c4d490$2a00a8c0@dash' \
--to=kewarken@qnx.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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