Date: Sat, 18 Nov 2000 11:53:54 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Rich Bud <rbud@fortean.com> Cc: freebsd-alpha@FreeBSD.ORG, deischen@FreeBSD.ORG, obrien@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: pthread_create under stable Message-ID: <14870.45447.43597.701639@grasshopper.cs.duke.edu> In-Reply-To: <Pine.BSF.4.21.0011172300200.1790-100000@chorizo> References: <Pine.BSF.4.21.0011172300200.1790-100000@chorizo>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't have a -stable alpha handy, but I think I'm seeing the same
problem under -current:
Starting program: /usr/src/lib/libc_r/test/hello_d
Program received signal SIGSEGV, Segmentation fault.
0x1600c1ff0 in _thread_kern_scheduler ()
at /usr/src/lib/libc_r/uthread/uthread_kern.c:177
177 if ((_thread_run->flags & PTHREAD_FLAGS_PRIVATE) == 0)
I don't know enough about how to debug threads to be very helpful
here. I did notice one rather disturbing warning though:
/usr/src/lib/libc_r/uthread/uthread_sig.c: In function `_thread_sig_wrapper':
/usr/src/lib/libc_r/uthread/uthread_sig.c:1003: warning: cast to pointer from integer of different size
(*(sigfunc))(psf->signo,
(siginfo_t *)psf->siginfo.si_code, &psf->uc);
si_code is a 32-bit int; you can't cast that to a 64-bit pointer on an
alpha and expect to have a useful pointer..
I hope one of the threads maintainers can figure it out prior to
4.2-RELEASE. This is a real show-stopper.
Also, I wonder if it is related to the crt0 changes?
Drew
Rich Bud writes:
> Has anyone else had problems with pthread_create under STABLE?
> As of a couple of weeks ago pthread_create has stopped working
> on my PW 500a. It now segfaults. I went to /usr/src/lib/libc_r/test
> and ran the tests there, and they all failed with the same problem.
> Here's the output from gdb with one of the libc_r tests:
>
> =======
> (gdb) run
> Starting program: /usr/src/lib/libc_r/test/./hello_d
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x1600bdcb0 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4
> =======
>
> This is after doing another buildworld this morning, but as i said
> it's been that way the last few builds i've done. Can anyone else
> confirm this problem, or do i need to start poking through my setup?
>
> Thanks,
> Rich Bud <rbud@fortean.com>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14870.45447.43597.701639>