Linonut <linonut@xxxxxxxxxxxxx> writes:
D> * dBera peremptorily fired off this memo:
>
>> On Jan 26, 12:05 pm, Linonut <lino...@xxxxxxxxxxxxx> wrote:
>>> * Roy Schestowitz peremptorily fired off this memo:
>>>
>>> > Open letter to OpenSUSE users [about Beagle]
>>>
>>> > ,----[ Quote ]
>>> >| * We would be extremely happy if beagle only used C# for all its operations.
>>> >| Unfortunately, we have to depend on a lot of C libraries for indexing certain
>>> >| files. Sometimes memory leaks (the C type) and segmentation faults happen in
>>> >| them. These are harder to spot since mono does not know about the memory
>>> >| allocated in the C libraries.
>>> > `----
>>>
>>> >http://dtecht.blogspot.com/2008/01/open-letter-to-opensuse-users.html
>>>
>>> Doesn't the Mono team know how to use valgrind?
>>
>> What has mono to do with C libraries ?
>
> Read the above. Valgrind will help them find the problems in the C
> libraries.
>
> And, after a couple minutes looking, I find that they /do/ seem to know
> about valgrind at Mono:
Pity you hadn't looked before showing off to the "advocates" eh?
>
> http://www.mono-project.com/Debugging#Using_Valgrind_on_Mono
>
> Using Valgrind on Mono
LOL
Liarnut tries a big "I am" and then falls flat on his face.
Ever the hard core developer eh?
And for those NOT in the know, garbage collection is nigh on impossible
for dynamic languages who can "hide" allocations from the memory master
...
,----
| Recent valgrind versions are able to deal with for self-modifying
| programs (which is what the mono JIT does) by using the --smc-check=all
| option.
`----
Valgrind has been extended to try to manage just that.
(before you start gobbing off, consider having a pointer to memory. You
then call a routine to "encode" that pointer as, say, an ascii string in
hex or somesuch. You then delete the pointer but do NOT call free or
equivalent. You then convert that ascii/hex string back to a memory
pointer. God help you if the GC has removed the memory. WTF?!?!?!?! I
never told it to do that .....)
|
|
