Possible.
On 7 May 2001, Dag-Erling Smorgrav wrote:
> Matthew Jacob <[EMAIL PROTECTED]> writes:
> > > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped)
> > (oh, yeah, a 4.1 built executable is dying, charming)
>
> That may well be a bug in your app. Xscreensaver, for instance, is
>
Matthew Jacob <[EMAIL PROTECTED]> writes:
> > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped)
> (oh, yeah, a 4.1 built executable is dying, charming)
That may well be a bug in your app. Xscreensaver, for instance, is
riddled with dangling-pointer and off-by-one bugs that rarely (if
On 03-May-01 Matthew Jacob wrote:
>
> T-o-T about 24 hours ago:
>
>> lock order reversal
>> 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239
>> 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542
>> 3rd 0xfeaab8d0 lockmgr interlock @
> /usr/
>
>
>http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=161827+165415+/usr/local/www/db/text/2001/freebsd-current/20010429.freebsd-current
>
Right- sorry to trouble you all.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 3 May 2001, Bruce A. Mah wrote:
> If memory serves me right, Matthew Jacob wrote:
>
> > T-o-T about 24 hours ago:
>
> ???
Top of Tree
> > > acquiring duplicate lock of same type: "allproc"
> > > 1st @ /usr/src/sys/kern/kern_proc.c:609
> > > 2nd @ /usr/src/sys/kern/kern_proc.c:146
On Thu, May 03, 2001 at 07:31:50AM -0700, Matthew Jacob wrote:
>
> T-o-T about 24 hours ago:
>
> > lock order reversal
> > 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239
> > 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542
> > 3rd 0xfeaa
If memory serves me right, Matthew Jacob wrote:
> T-o-T about 24 hours ago:
???
> > lock order reversal
> > 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239
> > 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542
> > 3rd 0xfeaab8d0 lockmgr i
