Created attachment 24726 [details]
screenshots

rimga: you should use localize, not localize_sl.

But i use localize (it is visible from screenshots also). localize_sl is 
called by localize script.

after looking at the sources it might be that you do not have a valid file at
%STAR_STANDLST

The linenumbers in the callstack would also help a lot to find the problem.

rimga,

You might run 'gwu.pl localize ...' instead of 'gwu.pl -env localize ...'. I
experienced same issue when I missed '-env'. The localize.exe (actaully
underlying filesystem handling layer) does not like unix paths in environment
variables.

Thanks jeongkyu, 
your comment helped. I think this issue can be closed.

.

closed

jeongkyu->ihi:

Please forgive me to reopen this issue. I believe that localize_sl could handle
the situation better than crash. For instance, it could display error message
such as mentioning '-env' in tcsh.

How do you think?

jeongkyu, do you want from every tool within the OOo buildssystem ( there are a
lot! ) to test if your environment is proper set ????

.

jeongkyu->ihi:

I didn't meant it. :-)

I used it for getting sdf file and putting it back to test localization issue. I
thought localize_sl is utility for localization. Also, I agree we don't need to
check if environment is set correctly. However, it would be better if we could
avoid crash (by checking 'null object'). 

Does it make sense to you?

I'll build in such a check

.