From: Kris Warkentin <kewarken@qnx.com>
To: GDB <gdb@sources.redhat.com>
Subject: in_solib_call_trampoline
Date: Wed, 27 Jul 2005 19:24:00 -0000 [thread overview]
Message-ID: <42E7E001.7030405@qnx.com> (raw)
Sorry for the dumb question but it's been a while since I brought my
head branch sandbox up to date. I'm sure I'm missing something obvious.
I was using set_gdbarch_in_solib_call_trampoline (gdbarch,
in_plt_section) so that I could step into solibs, much like many other
targets, but it looks like this method isn't supported anymore. Can
anyone tell me the accepted way to make gdb keep stepping past the plt
section and into the solib?
cheers,
Kris
--
Stay up-to-date on all the QNX news! Register at
http://www.qnx.com/news/forms/newsletter.html to
receive our newsletter.
next reply other threads:[~2005-07-27 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 19:24 Kris Warkentin [this message]
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
2005-07-28 10:18 in_solib_call_trampoline Randolph Chung
2005-08-05 20:01 ` in_solib_call_trampoline 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=42E7E001.7030405@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).