Date: Sat, 21 Jul 2001 19:56:20 -0700 From: Arun Sharma <arun@sharmas.dhs.org> To: hackers@freebsd.org Subject: Re: libc_r, signals and modifying sigcontext Message-ID: <20010721195620.A32616@sharmas.dhs.org> In-Reply-To: <20010721191747.A32529@sharmas.dhs.org>; from arun@sharmas.dhs.org on Sat, Jul 21, 2001 at 07:17:47PM -0700 References: <20010721191747.A32529@sharmas.dhs.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 21, 2001 at 07:17:47PM -0700, Arun Sharma wrote: > Greetings. I'm trying to port an application to FreeBSD. I have > a signal handler registered using signal(2). It modifies the > data pointed to by the third argument - of type sigcontext (specifically > sc_eip) - so that the execution would resume at a different point). > > However, when execution resumes, it resumes at the same point where > it was interrupted. A quick search of the archives brought up this > thread: Another data point: the problem doesn't happen with IBM's MxN pthread library ported to FreeBSD (mainly because it uses libc and not libc_r). http://oss.software.ibm.com/developerworks/opensource/pthreads/ I wonder how the scheduler activations based stuff is going to handle this case. -Arun 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?20010721195620.A32616>