From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kevin Buettner" <kevinb@redhat.com>,
"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: problem with fetch_link_map_offsets
Date: Tue, 29 Apr 2003 21:18:00 -0000 [thread overview]
Message-ID: <00e501c30e94$e285e400$0202040a@catdog> (raw)
In-Reply-To: <1030429162815.ZM6720@localhost.localdomain>
> > I also observe that svr4_have_link_map_offsets is called three times in
the
> > process of attaching to the remote proces. The first two are fine -
flmo is
> > still pointing to the qnx version. The third time it's pointing to the
> > legacy_flmo though. I can't figure out why.
>
> When you figure it out, let me know why too...
Interesting. I've been doing a refactor of our gdb port and, for no
particular reason, I started with sh4. Just for chuckles, I finished our
i386 port and I'm not getting the same "No shared library support" error. I
wonder if there's something specific in the sh4 version that's overriding my
settings. I was watching current_gdbarch and it did seem to be changing
quite a bit. Perhaps you're right and the problem lies in there.
cheers,
Kris
next prev parent reply other threads:[~2003-04-29 21:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 20:21 Kris Warkentin
2003-04-28 21:23 ` Andrew Cagney
2003-04-29 13:27 ` Kris Warkentin
2003-04-29 15:07 ` Kevin Buettner
2003-04-29 15:25 ` Kris Warkentin
2003-04-29 16:28 ` Kevin Buettner
2003-04-29 21:18 ` Kris Warkentin [this message]
2003-06-09 21:20 ` Kris Warkentin
2003-06-09 21:34 ` Kevin Buettner
2003-06-09 21:40 ` Kris Warkentin
2003-06-10 10:12 ` Richard Earnshaw
2003-06-10 12:21 ` Kris Warkentin
2003-06-10 12:26 ` Richard Earnshaw
2003-06-10 14:53 ` Kris Warkentin
2003-06-11 19:05 ` 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='00e501c30e94$e285e400$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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