From: Kris Warkentin <kewarken@qnx.com>
To: Randolph Chung <randolph@tausq.org>
Cc: drow@false.org, gdb@sources.redhat.com
Subject: Re: in_solib_call_trampoline
Date: Fri, 05 Aug 2005 20:01:00 -0000 [thread overview]
Message-ID: <42F3C65C.6040508@qnx.com> (raw)
In-Reply-To: <42E8B0F6.5000901@tausq.org>
Well, on the bright side, it turns out there's no problem with solibs
and backtraces. It turns out that I'm an idiot and chased this problem
all week only just now to notice that symbols weren't being loaded for
the solibs. So the problem is with auto-loading of symbols, not
backtracing and solib support.
On the bright side, in looking at the linux support, I was able to rip a
few things out of our tdep files and generally simplify things so it
wasn't a complete waste of a week. Still feel a bit of a dork though....;-)
Have a good weekend and thanks for the help.
cheers,
Kris
Randolph Chung wrote:
>>>I'm a bit confused here myself, but I have you taken a look at
>>>skip_trampoline_code?
>>>
>>>
>>I thought that gdbarch_skip_solib_resolver and
>>in_solib_dynsym_resolve_code would be enough. I'm not sure if all the
>>current skip_trampoline_code bits are necessary.
>>
>>
>
>Well, on hppa skip_trampoline_code knows about quite a few other types
>of trampolines in addition to solib PLT trampolines.
>
>randolph
>
>
--
Stay up-to-date on all the QNX news! Register at
http://www.qnx.com/news/forms/newsletter.html to
receive our newsletter.
next prev parent reply other threads:[~2005-08-05 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 10:18 in_solib_call_trampoline Randolph Chung
2005-08-05 20:01 ` Kris Warkentin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 19:24 in_solib_call_trampoline Kris Warkentin
2005-07-27 19:59 ` in_solib_call_trampoline Mark Kettenis
2005-07-27 20:02 ` in_solib_call_trampoline Kris Warkentin
2005-07-27 20:20 ` in_solib_call_trampoline Mark Kettenis
2005-07-27 20:07 ` in_solib_call_trampoline 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=42F3C65C.6040508@qnx.com \
--to=kewarken@qnx.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=randolph@tausq.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).