Juha Heinanen writes:
> INFO("Evaluating sst_config\n");
>
> call_profile.eval_sst_config(ctx,req,call_profile.sst_a_cfg);
>
> INFO("Done with evaluating sst_config\n");
>
> the latter is never executed.
i found and fixed the bug.
c++ sucks, because it does not tell where the exception was triggered.
c program would have crashed and i could have used gdb to find out
where. perhaps c++ is something similar i don't know about.
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
