Commit 1cf472fe authored by Jérome Perrin's avatar Jérome Perrin

software/theia: set TERMINFO

We are observing some segmentation fault with python curses applications
that might be because the TERMINFO are different from the system one.
I did not debugged, but since I set this environment variable I did not
observe any segmentation fault.

By comparing strace, the invocations seems same with or without $TERMINFO.
In both cases the termcaps from the correct ncurses are selected, this
just seem to workaround for some reason.
parent 97e7c8f6
...@@ -15,7 +15,7 @@ ...@@ -15,7 +15,7 @@
[instance] [instance]
filename = instance.cfg.in filename = instance.cfg.in
md5sum = 2ceb9389281c00261abd864fc8ed566f md5sum = 2f2bd31a4322fe46c3d7adf4443c9fba
[yarn.lock] [yarn.lock]
filename = yarn.lock filename = yarn.lock
......
...@@ -227,6 +227,7 @@ template = ...@@ -227,6 +227,7 @@ template =
export TMP=$${directory:tmp} export TMP=$${directory:tmp}
export TEMP=$TMP export TEMP=$TMP
export LC_ALL=C.UTF-8 export LC_ALL=C.UTF-8
export TERMINFO=${ncurses:location}/lib/terminfo/
export EDITOR="${python-language-server:location}/bin/python -m theia_open --wait" export EDITOR="${python-language-server:location}/bin/python -m theia_open --wait"
exec ${theia-wrapper:rendered} $@ exec ${theia-wrapper:rendered} $@
ip = $${instance-parameter:ipv4-random} ip = $${instance-parameter:ipv4-random}
......
  • for reference, the problem seems to happen less often with this change, but it still happen

Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment