Date: Sun, 29 Jul 2001 09:48:30 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Arun Sharma <arun@sharmas.dhs.org> Cc: hackers@FreeBSD.ORG Subject: Re: libc_r, signals and modifying sigcontext Message-ID: <Pine.SUN.3.91.1010729093922.16774A-100000@pcnet1.pcnet.com> In-Reply-To: <20010729011656.A11337@sharmas.dhs.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 29 Jul 2001, Arun Sharma wrote: > On Sun, Jul 22, 2001 at 10:50:01AM -0400, Daniel Eischen wrote: > > Dan, > > I tried this patch against 4.3-STABLE (had to substitute > _get_curthread() with _thread_run), without success. After > the sigreturn, EIP remains the same. Can you breakpoint or add a print statement to see if the thread chosen to handle the signal is the current thread (_thread_run == thread) in the patched section below? > > @@ -1059,6 +1064,8 @@ > > sizeof(psf->uc)); > > memcpy(&psf->siginfo, &_thread_sigq[psf->signo - 1].siginfo, > > sizeof(psf->siginfo)); > > + psf->restore_context = ((thread == _get_curthread()) && > > + (thread->ctxtype == CTX_UC)); > Should I be testing against -current ? No, -stable should be fine (other than the _get_curthread() vs _thread_run diff) -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1010729093922.16774A-100000>