Compile your application with the -verbose
flag, without the -no_warning flag, and with
all assertions on (default mode, or -all_check flag). This may
reveal a problem in the code you're trying to compile rather than in
SmartEiffel...
Then check the bug is not referenced in the bug database.
Do not hesitate to provide more details though.
A good and useful bug report -- that is, one that is more likely to be fixed -- is one that
respects the following simple guideline: BE PRECISE . More
precisely:
Try to isolate the problem on a small program, put this one
in your bug report with all instructions necessary to
reproduce the problem.
Don't forget to tell us the compilation command you used.
If for any reason you can't send us the small program mentioned
above, things may be much more difficult for us. So give us all
the relevant information you have. The
compilation command line that creates the problem (once again,
preferably, with the -verbose
flag, without the -no_warning flag, and with
all assertions on -- default mode, or -all_check
flag) and its verbose output. The execution stack trace you get in
case of a crash. Whether the problem occurs with any assertion
level or not. Whether the GC is concerned (try with and w/o the
-no_gc flag).