Date: Tue, 27 May 2003 14:10:41 -0400 (EDT) From: Daniel Eischen <eischen@pcnet1.pcnet.com> To: Petri Helenius <pete@he.iki.fi> Cc: freebsd-threads@freebsd.org Subject: Re: malloc(): error: recursive call Message-ID: <Pine.GSO.4.10.10305271407040.3076-100000@pcnet1.pcnet.com> In-Reply-To: <02d801c3247a$3b347710$812a40c1@PETEX31>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 May 2003, Petri Helenius wrote: > > > > Are you linking to libkse before linking to libc? (Don't explicitly > > link to libc). Or are you linking to other libraries that are linked > > to libc_r? > > > I=B4m linking to -lnetsnmp and -lcrypto and -lpcap. -lkse is last on the = command > line. And what does `ldd libnetsnmp.so.x`, `ldd libfoo.y`, show? What is `ldd yourexecutable` show? > > We haven't had any problems like that in all of our tests. > > > This seems to happen even on single-cpu machine. __isthreaded is 1 if I m= ake the > process dump core. >=20 > Anything else I should look for? Try with libthr ? malloc is thread safe and we've been using it fine with all our tests. I suspect you're using another library that is using libc_r or something. --=20 Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10305271407040.3076-100000>