Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tcf-dev] The 'terminate' command in Processes service doesn't work

Thanks for your reply, Eugene. I wonder if it has something to do with the distribution/version of Linux. As suggested, I have filed a bug report. I included the toy program and a bit more detail about my Ubuntu machine in there.


https://bugs.eclipse.org/bugs/show_bug.cgi?id=526536


Please take a look. Thanks!


--Dato

On October 26, 2017 at 2:38 PM Eugene Tarassov <eugenet@xxxxxxxxxx> wrote:

Hi Dato,

 

This does look like a bug.

However, I tried your steps on my Linux machine using latest agent, and it worked fine.

So, the issue is not easily reproducible. It can be something specific to either your executable or to your Linux version.

I suggest to create a bug report and attach Hello_Worl_Loop executable to it.

 

Regards,

Eugene

 

 

From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Da Dato
Sent: Thursday, October 26, 2017 10:14 AM
To: tcf-dev@xxxxxxxxxxx
Subject: [tcf-dev] The 'terminate' command in Processes service doesn't work

 

Hi,

 

    I can't get the terminate command to work with the agent built from master. Here's a reproducer:

 

1. Environment: Ubuntu 16.04

2. Start the agent in one console:

    $ ./agent &

3. Start the client in another console, and do the following in the client

   > connect tcp::1534
   Connection established with TCP:127.0.0.1:1534
   > tcf Processes start "/tmp" "/home/Hello_World_Loop/Debug/Hello_World_Loop" [] [] false
  {"Name":"[Hello_World_Loop]","CanTerminate":true,"StdInID":"VS0","StdOutID":"VS1","StdErrID":"VS2","ID":"P19231"}
   > tcf Processes terminate "P19231"

4. Now, go back to the first console, and do

    $ pgrep -a Hello_Wrold_Loop

    You would still see the Hello_World_Loop in the output.

 

I tried a few other tags in the repo. 1.4_neon and 1.5_oxygen both suffer the same problem, whereas 1.3.0 doesn't (i.e., the process does get killed after the terminate command is issued).

 

Does this look like a bug, or am I missing something when starting the process? Any input would be appreciated. Thanks!

 

--Dato


Back to the top