Stephen Montgomery-Smith wrote:
I notice that if you use "malloc" from within a signal handler on
FreeBSD-6.x, that you can potentially trigger a "recursive call" error.
But this seems to have changed in FreeBSD-7.x.
The malloc implementation is completely new in FreeBSD 7, so not all of
the
Ivan Voras wrote:
I think this is the major change in malloc between 7.0 and 7.1:
http://svn.freebsd.org/viewvc/base?view=revision&revision=184602
You can test if it's the cause of your problem by toggling between 'D'
and 'M' options to malloc.conf (see malloc(3), don't forget to restart
apache)
Joshua Coombs wrote:
Derek Taylor wrote:
On Fri, Feb 29, 2008 09:50 PM Sean <[EMAIL PROTECTED]> wrote:
Check /etc/make.conf for CFLAGS, and if present remove it.
This fixed the problem.
Thank you.
-Derek.
I can confirm a failure in the same spot. What concerns me is in both
my failure,
Disregard my previous email. After looking at the test more closely, I see
that it is necessary to press enter soon after starting the test to cause
the failure. I'm looking into the problem now.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body
Attached is a patch for -stable that should fix the problem your test
exposes, as well as a problem that your actual program might hit (canceled
threads should not detach). I also noticed and hopefully fixed a problem
with canceling a thread suspended while joining, but you probably don't do
that
