Conversation
By launching in a PTY the `bash -i` won't have its stdin connected to the stdin of Eclipse, meaning it will properly behave and not stop with a SIGTTIN when bash tries to read. Fixes #626
|
This seems to be the correct fix. But I am letting this build on CI so that I can have a p2 to install on multiple machines easier to facilitate testing. This works in my linux dev environment when launched from a terminal or from a UI. This is building on Jenkins now and will be ready as a p2 site in a little while here: https://download.eclipse.org/embed-cdt/builds/launch-xpm-in-pty/ I will progress this again tomorrow. @ilg-ul Once I have tested this I will let you know so you can test in your environment too. |
|
I checked the new p2 site and it was ok on my RPi5, with Eclipse started both in a terminal or from the file manager. Can you help me understand your solution? |
Just to be sure, did you install node/npm via nvm, as instructed? |
Yes. |
|
I have tested it by installing https://download.eclipse.org/embed-cdt/builds/launch-xpm-in-pty/p2/ into Eclipse IDE for Embedded C/C++ developers 2026-02 M2. Without the update it hangs (when launched from terminal) and with the update it creates project as expected. I will now test on a Windows (and maybe a macOS machine if I can borrow one).
By adding the PTY argument ( This allows launching |
By launching in a PTY the
bash -iwon't have its stdin connected to the stdin of Eclipse, meaning it will properly behave and not stop with a SIGTTIN when bash tries to read.Fixes #626