From: "Boehm, Hans" <hans_boehm@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] getcontext() correctly implemented ?
Date: Fri, 21 Sep 2001 21:28:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805238@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805230@msgid-missing>
In the threads case, I intercept thread creation, and thus capture the
backing store pointer on thread startup. For the main thread, I use the
variable if its available (glibc 2.2.4+ ?), and a rather brittle heuristic
(which happens to work on current kernels) if it's not.
Hans
> -----Original Message-----
> From: stefan [mailto:stefan@lkcc.org]
> Sent: Friday, September 21, 2001 7:12 AM
> To: David Mosberger
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] getcontext() correctly implemented ?
>
>
> On Thu, 20 Sep 2001, David Mosberger wrote:
>
> > You didn't mention the register backing store. Be sure to scan that
> > one too! For the main thread, libc exports a global variable which
> > will help you find the beginning of the backing store. The variable
> > is called "__libc_ia64_register_backing_store_base". I'm not sure
> > what pthreads does (Hans can you help?). The top of the register
> > backing store can be obtained from the "sc_bsp" member in
> the ucontext
> > (uc->uc_mcontext.sc_bsp).
>
> Wow ! This fixed this specific problem. With a little change:
> uc->uc_mcontext.sc_bsp is uc->uc_mcontext.sc_ar_bsp.
>
> Thanks a lot,
> stefan@lkcc.org
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
prev parent reply other threads:[~2001-09-21 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 17:34 [Linux-ia64] getcontext() correctly implemented ? stefan
2001-09-20 18:26 ` David Mosberger
2001-09-20 22:09 ` stefan
2001-09-20 22:58 ` David Mosberger
2001-09-21 8:41 ` Andrew Haley
2001-09-21 14:11 ` stefan
2001-09-21 21:28 ` Boehm, Hans [this message]
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=marc-linux-ia64-105590698805238@msgid-missing \
--to=hans_boehm@hp.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.