On Wednesday 24 August 2005 07:04, Hannah Schroeter wrote: > A few things that get bitten are some packages doing their own and very > different memory management, but can't avoid malloc altogether. > That is ports/lang/clisp, that seems to be also gprolog
Can you describe how these programs manage to seg fault doing their memory management? How do they run now if they don't use malloc? -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
