In message <[EMAIL PROTECTED]>, Pascal Hofste
e writes:
>On Sat, Jul 15, 2000 at 11:36:30AM +0200, Paul Herman wrote:
>> On Sat, 15 Jul 2000, Pascal Hofstee wrote:
>>
>> > Since a recent update of my CURRENT system i get weird coredumps from at
>> > least two applications which just worked fine previously. The two programs
>> > are tintin++ (mud-client) ... and licq (when trying to set myself to
>> > "away-mode").
>>
>> Just a wild guess, but this could be because of the recently added
>> /etc/malloc.conf options -- (which are just for debuging purposes for
>> now...)
>
>Well ... for a wild guess it was Right On Top ...
>
>After searching the freebsd-current mailling list i located the bit about
>malloc.conf
>
>ln -sf j /etc/malloc.conf <--- fixed the problems i was having
No, not "fixing the problems", "obscuring the problems".
The tintin++ code contains errors, and you should fix them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
