> I was wondering what things you did to isolate the problem?
Right now, I was probably the only person who could have debugged
this easily, it required having sfront generate a few printf's at
key places in the memory management code.
Things will get better quite soon in this department, though,
I'm currently working on updating the control driver API, to
support a wider range of applications, including symbolic
debuggers and dynamic handling of SA_access_units (note that
sfront 0.57 can syntactically read SA_access_units in .sa
files, and compile them into an sa.c file, but this isn't
truly streaming of course, it's batch-mode processing). This
sort of interface, combined with implementing printf()'s as
an sfront-specific SAOL construct (like idump and kdump are
saolc-specific constructs), should bring debugging SAOL out
of the stone age. The next release will definitely include
the improved control driver API, it may or may not include
printf()'s though ...
--jl
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 12:03:53 EST