Re: [Serusers] [Serdev] [Tracker] Reopened: (SER-263) Using @select=~ "regexp" causes segmentation fault

Samuel, yes it is related to. The resolution of SER-263 was wrong and every test like if (@select=="") has returned false, even the return value of the select was empty string. But, there is another problem I see in the config (including the example script)... There is difference between the (@select) test and (@select!="") one. The latter returns false, if the select framework returns N/A value (e.g. non present header/parameter). Intended behaviour was: @X is @route[1].params.lr in this example (as the tag must have value if present rfc3261 19.3) lr parameter test result not present @X false !@X true @X=="" FALSE* @X!="" FALSE* lr @X true !@X false @X=="" true @X!="" false lr=123 @X true !@X false @X=="" false @X!="" true As I see the from the example ser.cfg, the tests are done in the (@to.tag=="") way, which won't work if the to.tag would return either N/A or the tag value. But it seems it returns the empty string even if not present, because it was previously working. So I ask the community (especially TB potential members) do we want to take care about the select N/A value differently, or shall we make it equal to empty string? Note, that if the answer is yes, it will be very hard to differentiate between parameter not present and parameter without value - well the lr parameter is handled internally, but what others? If the anwser is no, keep special N/A value handling, the select must be reviewed together with the ser.cfg, because (@to.tag=="") will be false for every tag (because it must have value). Michal On Čt, 2007-06-07 at 13:56 +0200, samuel wrote: