Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>, <kevinb@redhat.com>
Subject: Re: problem with fetch_link_map_offsets
Date: Tue, 29 Apr 2003 13:27:00 -0000	[thread overview]
Message-ID: <024001c30e53$0fcccba0$0202040a@catdog> (raw)
In-Reply-To: <3EAD9BB8.8050205@redhat.com>

> > All of a sudden I'm getting a complaint about "No shared lib support for
> > this OS/ABI" from the new svr4_have_link_map_offsets function.  When I
> > initialize my backend tdep file, I set the fetch_link_map_offsets
function.
> > If I break on svr4_fetch_link_map_offsets, the first couple times I see
that
> > flmo is set to my function, then the third time it's been set back to
> > legacy_fetch_link_map_offsets.  I set a break on
> > set_solib_svr4_fetch_link_map_offsets and see it being called with my
> > function but it never gets called again between when I set it and when
it
> > shows up as changed.
> >
> > Can someone tell me where to set a watchpoint to catch the gdbarch data
> > being set?  I'm still a little shakey on how that all works.
>
> An aside, "set debug arch 1", and watch to see if any other
> architectures are being initialized or selected.

Wow...talk about verbosity.  At least now I've ruled out any other arches
being selected.  I was pretty sure that they weren't because I had set a
break on set_solib_svr4_fetch_link_map_offsets and it was only called by us.
Since that's the only interface to change the lmo function, it would seem
like it has to be happening in the solib-svr4.c file somewhere.  That's why
I was hoping to set a watchpoint.

cheers,

Kris


  reply	other threads:[~2003-04-29 13:27 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 [this message]
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
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='024001c30e53$0fcccba0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.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