From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: kewarken@qnx.com
Cc: gdb@sources.redhat.com
Subject: Re: in_solib_call_trampoline
Date: Wed, 27 Jul 2005 20:20:00 -0000 [thread overview]
Message-ID: <200507272020.j6RKKMsf019569@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <42E7E901.5080305@qnx.com> (message from Kris Warkentin on Wed, 27 Jul 2005 16:05:21 -0400)
Date: Wed, 27 Jul 2005 16:05:21 -0400
From: Kris Warkentin <kewarken@qnx.com>
Well, I've been looking at the frame_unwind_sniffers...I guess I'll try
that next. Kind of annoying not being able to step into shared libs
anymore. ;-)
Having you target unwind from within .plt is a good idea anyway; your
program might end up there once in a while if it encounters a random
signal.
Mark
next prev parent reply other threads:[~2005-07-27 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Mark Kettenis [this message]
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=200507272020.j6RKKMsf019569@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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).