On Fri, Apr 20, 2012 at 17:21, Andres Cimmarusti <[email protected]> wrote:
> One way of triggering the problem, that I recently discovered, is to > incorrectly load the data (using the command line in the GUI). This > causes fityk to segfault instead of giving the correct error message. I remember this problem, errors from xylib were not handled properly in fityk. I think it was fixed before 0.9.8, but please check it. Cheers Marcin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
