I mentioned earlier on this mailing list a problem ("segmentation
fault": usually the sign of a memory allocation gone wrong) which
occurs when merely substituting
isalnum()
for
issspace ()
in a simplistic scanner, see:
http://mail.gnome.org/archives/vala-list/2011-June/msg00062.html
This simple substitution produces a totally unexpected segmentation
fault when the application (see link above) is run on a text file a
few hundreds of MB large.
- Is there a way to try to assess what went wrong ?
- Is there a Valgring-like utility for Vala ?
- Does anybody have an idea why this is happening ?
- Can Vala be trusted to develop non-trivial applications (is it ripe,
debugged, tested, robust enough) ?
Serge.
_______________________________________________
vala-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/vala-list
