On Mon, 14 Dec 2009, Sven Schreiber wrote:
ok, problem resolved, after a reboot no crash occurs anymore, so it
wasn't gretl's fault it seems. Funny though how Linux resembles Windows
more and more, now even reboots are necessary to fix problems... ;-)
Unless you updated from CVS in the last 2 minutes, the problem
was not solved! Sometimes you "get lucky" and a memory management
fault doesn't cause a crash. But in fact this is unlucky from the
coder's point of view because it masks the problem.
Hint: anyone using gretl built from CVS might want to consider
building with debugging symbols on ("-g") and then running gretl
under valgrind when this sort of issue occurs. Valgrind usually
manages to spot exactly where the error is, whether or not it
actually produces a crash.
Allin