Date: Wed, 15 Jul 1998 07:02:00 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: tlambert@primenet.com (Terry Lambert) Cc: andre@pipeline.ch, pvh@leftside.wcape.school.za, freebsd-hackers@FreeBSD.ORG Subject: Re: Detecting the presence of threads (for a port) Message-ID: <199807150702.AAA08476@usr06.primenet.com> In-Reply-To: <199807150629.XAA06869@usr06.primenet.com> from "Terry Lambert" at Jul 15, 98 06:29:06 am
next in thread | previous in thread | raw e-mail | index | archive | help
> For what it's worth, the code with all the agregate patches I did, > plus all of my own patches I did on top of that, appears to run fine > on RedHat Linux. > > The bug is a result of linking the dbm stuff against libc_r, and is > a libc_r bug, not a bug in the patches. Oops. I may have spoke too soon. If the patches posted here by another able engineer actually work, this is tantamount to the common Linux assumption of bzero'ed stack pages for sockaddr_in structs... in other words, a real coding error, not a threads bug on BSD. If this holds true, my theory is that the user space nature of the threads triggered the bug by scribbling on the stack before it was used (something that should not have caused a problem, but did because of the coding error). This is totally cool. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?199807150702.AAA08476>